All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: "Uwe Kleine-König" <uwe@kleine-koenig.org>
Cc: Christopher Li <sparse@chrisli.org>,
	Ramsay Jones <ramsay@ramsayjones.plus.com>,
	Linux-Sparse <linux-sparse@vger.kernel.org>,
	873508@bugs.debian.org, Antoine Beaupre <anarcat@debian.org>
Subject: Bug#873508: sparse test failures on ppc32le (and other not so common archs)
Date: Sun, 10 Sep 2017 14:29:07 +0200	[thread overview]
Message-ID: <CAExDi1Tz0Y=TVt2QDB2tJ4H4fcgczTe3JEuMvVWWGsHhN2JSOA@mail.gmail.com> (raw)
In-Reply-To: <df2139ba-8ac3-00c7-5c46-896f15c13671@kleine-koenig.org>

On Sun, Sep 10, 2017 at 10:43 AM, Uwe Kleine-König
<uwe@kleine-koenig.org> wrote:
>
>> Meanwhile, is it possible to have the build logs but with 'make V=1 ...' ?
>> It would also be useful to have:
>> - the output of 'uname -a'
>> - the details about the version of LLVM you're using
>
> Sure, can do. Attached is a build from the ppc64el machine with Chris'
> patch applied. Tell me if it contains everything you need.

I've taken a look at it what happens.
The problem is easy to identify and very annoying to solve:
in sparsec (a wrapper for sparse-llvm + llc + as [+ ld]) there
is a discrepancy between the defaults for llc and as.
'llc' seems to default to the sub-architecture of the build machine
(possibly including the most modern features) while 'as' defaults
to the minimal features for the build machine architecture.

The problem can be solved (on the machine I have access to) by either:
- using the option "-mgeneric" for llc
- using the option "-mpower8" for as

Something smarter would be better.

-- Luc

  parent reply	other threads:[~2017-09-10 12:29 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <150392922734.24087.13050909898214597041.reportbug@curie.anarc.at>
2017-08-30 16:14 ` Bug#873508: sparse test failures on ppc32le (and other not so common archs) Uwe Kleine-König
2017-08-30 16:55   ` Ramsay Jones
2017-08-30 17:36     ` Uwe Kleine-König
2017-08-31  0:11       ` Christopher Li
2017-08-31 20:55         ` Uwe Kleine-König
2017-08-31 22:43           ` Ramsay Jones
2017-09-01  0:50             ` Christopher Li
2017-09-01  7:46             ` Uwe Kleine-König
2017-09-01 11:51               ` Christopher Li
2017-09-21 18:58               ` Bug#873508: " Uwe Kleine-König
2017-09-26 18:11                 ` Uwe Kleine-König
2017-09-27  8:00                   ` Uwe Kleine-König
2017-09-27  8:40                     ` Luc Van Oostenryck
2017-09-27 21:11                     ` [PATCH] fix cgcc ELF version for ppc64/pcc64le Luc Van Oostenryck
2017-09-30  8:49                       ` Uwe Kleine-König
2017-10-02 19:45                         ` Luc Van Oostenryck
2017-10-02 21:17                           ` Christopher Li
2017-10-03  4:46                       ` Christopher Li
2017-09-01  0:47           ` sparse test failures on ppc32le (and other not so common archs) Christopher Li
2017-09-01  7:02             ` Josh Triplett
2017-09-01  7:57               ` Uwe Kleine-König
2017-09-01 22:55                 ` Josh Triplett
2017-09-01 12:00               ` Christopher Li
2017-09-03 21:14               ` Luc Van Oostenryck
2017-09-04 18:00                 ` Christopher Li
     [not found]                 ` <715b7059-4ff0-0982-ff92-56c13c4160e7@kleine-koenig.org>
     [not found]                   ` <CAMHZB6GHoA6v_RPtKF3WBbX0DPB5pqfz9wLf1iP8MWfUVdbteQ@mail.gmail.com>
2017-09-06 14:44                     ` Uwe Kleine-König
2017-09-06 15:18                       ` Christopher Li
2017-09-06 15:36                         ` Uwe Kleine-König
2017-09-12  5:59                           ` Christopher Li
2017-09-12  6:27                             ` Uwe Kleine-König
2017-09-12  6:36                               ` Christopher Li
2017-09-09 21:02             ` Uwe Kleine-König
2017-09-10  1:56               ` [PATCH] build: disable sparse-llvm on non-x86 Luc Van Oostenryck
2017-09-12  6:02                 ` Christopher Li
2017-09-12  6:12                   ` Luc Van Oostenryck
2017-09-12  6:27                     ` Christopher Li
2017-09-12  6:34                       ` Luc Van Oostenryck
2017-09-12  6:44                         ` Christopher Li
2017-09-12  6:48                           ` Luc Van Oostenryck
2017-09-12  7:04                             ` Christopher Li
2017-09-12  7:01                 ` Christopher Li
2017-09-12  7:10                   ` Luc Van Oostenryck
2017-09-12 15:53                     ` Christopher Li
2017-09-01 11:33 ` Bug#873508: sparse test failures on ppc32le (and other not so common archs) Antoine Beaupré
2017-09-10  1:22 ` Luc Van Oostenryck
2017-09-10  8:43   ` Uwe Kleine-König
2017-09-10  9:39     ` Luc Van Oostenryck
2017-09-10 12:29 ` Luc Van Oostenryck [this message]
2018-04-27  5:56 ` Bug#873508: " Uwe Kleine-König
2018-04-27  7:33 ` Bug#873508: sparse test failures & PATH_MAX Luc Van Oostenryck
2018-04-27  7:33 ` Uwe Kleine-König
2018-04-27  7:43 ` Bug#873508: sparse test failures on x32 Luc Van Oostenryck
2018-04-27 16:11 ` Bug#873508: sparse test failures & PATH_MAX Luc Van Oostenryck
2019-01-10  2:28 ` Bug#873508: sparse test failures on ppc32le (and other not so common archs) Antoine Beaupré
2019-01-10 11:39 ` Luc Van Oostenryck

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAExDi1Tz0Y=TVt2QDB2tJ4H4fcgczTe3JEuMvVWWGsHhN2JSOA@mail.gmail.com' \
    --to=luc.vanoostenryck@gmail.com \
    --cc=873508@bugs.debian.org \
    --cc=anarcat@debian.org \
    --cc=linux-sparse@vger.kernel.org \
    --cc=ramsay@ramsayjones.plus.com \
    --cc=sparse@chrisli.org \
    --cc=uwe@kleine-koenig.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.