public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug regression/46667] Target arm-unknown-eabi build results in "causes a section type conflict" error in libstdc++
Date: Fri, 26 Nov 2010 01:29:00 -0000 [thread overview]
Message-ID: <bug-46667-4-emCUIIzUC0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46667-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46667
Zdenek Sojka <zsojka at seznam dot cz> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |zsojka at seznam dot cz
--- Comment #1 from Zdenek Sojka <zsojka at seznam dot cz> 2010-11-26 00:52:20 UTC ---
This probably isn't specific to arm, I am getting the same error at
x86_64-linux with -freorder-blocks-and-partition -g:
----- testcase.c -----
void foo() {}
----------------------
$ gcc -freorder-blocks-and-partition -g testcase.c
testcase.c: In function 'foo':
testcase.c:1:6: error: foo causes a section type conflict
testcase.c:1:6: error: foo causes a section type conflict
testcase.c:1:6: error: foo causes a section type conflict
next prev parent reply other threads:[~2010-11-26 0:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-26 1:16 [Bug regression/46667] New: " John.Tytgat at aaug dot net
2010-11-26 1:29 ` zsojka at seznam dot cz [this message]
2010-11-26 12:20 ` [Bug regression/46667] " ramana at gcc dot gnu.org
2010-11-26 16:02 ` [Bug middle-end/46667] [4.6 Regression] -freorder-blocks-and-partition -g failed hjl.tools at gmail dot com
2010-11-26 17:20 ` [Bug middle-end/46667] [4.6 Regression] -freorder-blocks-and-partition -g failed and libstdc++ builds for arm-eabi are broken ramana at gcc dot gnu.org
2010-11-29 23:48 ` John.Tytgat at aaug dot net
2010-12-01 20:36 ` joel at gcc dot gnu.org
2010-12-02 17:53 ` ramana at gcc dot gnu.org
2010-12-02 17:54 ` ramana at gcc dot gnu.org
2010-12-03 3:38 ` jiez at gcc dot gnu.org
2010-12-03 4:23 ` jiez at gcc dot gnu.org
2010-12-14 13:07 ` hubicka at gcc dot gnu.org
2010-12-14 13:09 ` hubicka 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-46667-4-emCUIIzUC0@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: 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).