public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sebastian.huber@embedded-brains.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/55033] [4.6/4.7/4.8 Regression] PowerPC section type conflict error
Date: Tue, 06 Nov 2012 13:18:00 -0000 [thread overview]
Message-ID: <bug-55033-4-DZ8oL6smvv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55033-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55033
--- Comment #4 from Sebastian Huber <sebastian.huber@embedded-brains.de> 2012-11-06 13:18:15 UTC ---
(In reply to comment #3)
> Would this be testable on powerpc-apple-darwin8?
See also
http://gcc.gnu.org/ml/gcc-patches/2012-10/msg02051.html
The -mcpu=8540 -msdata=eabi option is important. I don't know how to trigger
this bug without the -mcpu=8540 option.
next prev parent reply other threads:[~2012-11-06 13:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 12:54 [Bug c++/55033] New: " sebastian.huber@embedded-brains.de
2012-10-23 13:21 ` [Bug c++/55033] " sebastian.huber@embedded-brains.de
2012-10-23 15:03 ` [Bug target/55033] " sebastian.huber@embedded-brains.de
2012-11-06 9:27 ` fang at csl dot cornell.edu
2012-11-06 13:18 ` sebastian.huber@embedded-brains.de [this message]
2012-11-25 15:58 ` rguenth at gcc dot gnu.org
2012-12-03 16:04 ` rguenth at gcc dot gnu.org
2013-03-26 16:11 ` [Bug target/55033] [4.6/4.7/4.8/4.9 " joel at gcc dot gnu.org
2013-04-12 15:16 ` [Bug target/55033] [4.7/4.8/4.9 " jakub at gcc dot gnu.org
2013-05-10 2:10 ` amodra at gmail dot com
2013-06-12 15:29 ` pthaugen at gcc dot gnu.org
2013-06-13 9:10 ` sebastian.huber@embedded-brains.de
2013-07-02 4:39 ` jasonwucj at gmail dot com
2014-06-12 13:44 ` [Bug target/55033] [4.7/4.8/4.9/4.10 " rguenth at gcc dot gnu.org
2014-06-12 15:42 ` [Bug target/55033] [4.8/4.9/4.10 " amodra at gmail dot com
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-55033-4-DZ8oL6smvv@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).