From: Paulo Matos <pmatos@linki.tools>
To: Christophe Lyon <christophe.lyon@linaro.org>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: GCC Buildbot Update
Date: Fri, 15 Dec 2017 09:19:00 -0000 [thread overview]
Message-ID: <61dee997-5760-63ac-8a7d-d901e60fa771@linki.tools> (raw)
In-Reply-To: <CAKdteObvKKTJrpq2Mod-9H37QpiT2gPshgfeztWJvi-XLQE-sw@mail.gmail.com>
On 14/12/17 21:32, Christophe Lyon wrote:
> Great, I thought the CF machines were reserved for developpers.
> Good news you could add builders on them.
>
Oh. I have seen similar things happening on CF machines so I thought it
was not a problem. I have never specifically asked for permission.
>> pmatos@gcc115:~/gcc-8-20171203_BUILD$ as -march=armv8.1-a
>> Assembler messages:
>> Error: unknown architecture `armv8.1-a'
>>
>> Error: unrecognized option -march=armv8.1-a
>>
>> However, if I run the a compiler build manually with just:
>>
>> $ configure --disable-multilib
>> $ nice -n 19 make -j4 all
>>
>> This compiles just fine. So I am at the moment attempting to investigate
>> what might cause the difference between what buildbot does and what I do
>> through ssh.
>>
> I suspect you are hitting a bug introduced recently, and fixed by:
> https://gcc.gnu.org/ml/gcc-patches/2017-12/msg00434.html
>
Wow, that's really useful. Thanks for letting me know.
--
Paulo Matos
next prev parent reply other threads:[~2017-12-15 9:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-14 8:56 Paulo Matos
2017-12-14 11:39 ` David Malcolm
2017-12-15 9:16 ` Paulo Matos
2017-12-15 14:29 ` David Malcolm
2017-12-16 11:07 ` Paulo Matos
2018-01-24 19:20 ` jamais-vu can now ignore renumbering of source lines in dg output (Re: GCC Buildbot Update) David Malcolm
2018-01-25 7:25 ` Paulo Matos
2018-01-29 13:55 ` Paulo Matos
2018-01-29 14:19 ` David Malcolm
2018-01-29 14:27 ` Paulo Matos
2017-12-14 20:32 ` GCC Buildbot Update Christophe Lyon
2017-12-15 7:42 ` Markus Trippelsdorf
2017-12-15 9:21 ` Paulo Matos
2017-12-15 11:10 ` Markus Trippelsdorf
2017-12-15 17:05 ` Segher Boessenkool
2017-12-16 11:54 ` Paulo Matos
2017-12-15 9:19 ` Paulo Matos [this message]
2017-12-15 9:21 ` Christophe Lyon
2017-12-15 9:29 ` Paulo Matos
2017-12-20 8:32 ` Paulo Matos
2017-12-20 9:52 ` Christophe Lyon
2017-12-20 10:02 ` Paulo Matos
2017-12-20 10:09 ` Christophe Lyon
2017-12-20 11:49 ` James Greenhalgh
2017-12-20 14:01 ` Paulo Matos
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=61dee997-5760-63ac-8a7d-d901e60fa771@linki.tools \
--to=pmatos@linki.tools \
--cc=christophe.lyon@linaro.org \
--cc=gcc@gcc.gnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).