public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "williambader at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/48431] New: patch to fix a compile error in lto-plugin.c when using older C compilers Date: Mon, 04 Apr 2011 03:53:00 -0000 [thread overview] Message-ID: <bug-48431-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48431 Summary: patch to fix a compile error in lto-plugin.c when using older C compilers Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: lto AssignedTo: unassigned@gcc.gnu.org ReportedBy: williambader@hotmail.com Created attachment 23867 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=23867 patch to fix the problem The build for gcc-4.6.0 gets a compile error on lto-plugin.c on Red Hat Linux release 7.1 (Seawolf) with gcc version 2.96 20000731 because this compiler does not allow declarations after the first statement. The attached patch moves a declaration a few lines back. For the build, I ran /u/gnu/gcc-4.6.0/configure --disable-nls --enable-checking=release --enable-werror=no --with-system-zlib --disable-multilib --with-gmp=/usr/local --with-mpfr=/usr/local make CC=gcc 'CFLAGS=-O0 -g -pipe' 'LIBCFLAGS=-O0 ' 'LIBCXXFLAGS=-O0 -fno-implicit-templates ' 'CXXFLAGS=-O0 -fno-implicit-templates ' 'CXXFLAGS_FOR_BUILD=-O0 -fno-implicit-templates ' 'CXXFLAGS_FOR_TARGET=-O0 -fno-implicit-templates ' 'GOCFLAGS_FOR_TARGET=-O0 -g -pipe' 'BOOT_CFLAGS= -O0 -g -pipe' AS=/usr/bin/as bootstrap-lean Without all of the -O0's, the stage2 xgcc gets an ICE almost immediately on almost any input.
next reply other threads:[~2011-04-04 3:53 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-04-04 3:53 williambader at hotmail dot com [this message] 2011-04-04 12:40 ` [Bug lto/48431] " rguenth at gcc dot gnu.org 2011-04-05 12:20 ` rguenth at gcc dot gnu.org 2011-04-05 12:24 ` rguenth at gcc dot gnu.org 2011-04-05 12:28 ` rguenth at gcc dot gnu.org
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=bug-48431-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).