From: Thomas Schwinge <thomas@codesourcery.com>
To: Matthias Klose <doko@ubuntu.com>
Cc: Andrew Stubbs <ams@codesourcery.com>,
Tobias Burnus <tobias@codesourcery.com>, <gcc-help@gcc.gnu.org>
Subject: GCC 10, nvptx target: newlib build failure?
Date: Tue, 16 Jun 2020 20:59:38 +0200 [thread overview]
Message-ID: <yxfpmu527s6d.fsf@hertz.schwinge.homeip.net> (raw)
Hi Matthias!
Andrew relayed the following to me:
<doko> ams_cs, Tobias__: can you build the nvptx offload compiler on the branch? I get:
<doko> In file included from /<<PKGBUILDDIR>>/src-nvptx/newlib/libc/include/ssp/stdio.h:34,
<doko> from /<<PKGBUILDDIR>>/src-nvptx/newlib/libc/include/stdio.h:800,
<doko> from ../../../../../../src-nvptx/newlib/libc/stdio/gets.c:62:
<doko> ../../../../../../src-nvptx/newlib/libc/stdio/gets.c:96:1: error: expected declaration specifiers or '...' before '__builtin_object
<doko> _size'
<doko> 96 | gets (char *buf)
<doko> | ^~~~
<doko> make[10]: *** [Makefile:1096: lib_a-gets.o] Error 1
<doko> this is newlib 3.3.0, unchanged from the previous build
<doko> gcc-10 branch
Earlier today, I built releases/gcc-10 branch at commit
7d249d84e4c1be7c6f857c3a9d7791623a0e9d00, with newlib at commit
6d79e0a58866548f435527798fbd4a6849d05bc7 (tag: newlib-3.3.0),
successfully.
Tobias also stated that he "did a build of GCC 10 (the branch) and it did
*not* fail".
Hmm.
Do you have any local patches applied that might be relevant?
Grüße
Thomas
-----------------
Mentor Graphics (Deutschland) GmbH, Arnulfstraße 201, 80634 München / Germany
Registergericht München HRB 106955, Geschäftsführer: Thomas Heurung, Alexander Walter
next reply other threads:[~2020-06-16 18:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 18:59 Thomas Schwinge [this message]
2020-07-17 12:04 ` Matthias Klose
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=yxfpmu527s6d.fsf@hertz.schwinge.homeip.net \
--to=thomas@codesourcery.com \
--cc=ams@codesourcery.com \
--cc=doko@ubuntu.com \
--cc=gcc-help@gcc.gnu.org \
--cc=tobias@codesourcery.com \
/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).