public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ak at muc dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/24585] spurious section conflict error while building linux kernel
Date: Sun, 30 Oct 2005 15:56:00 -0000 [thread overview]
Message-ID: <20051030155645.17465.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24585-7834@http.gcc.gnu.org/bugzilla/>
------- Comment #1 from ak at muc dot de 2005-10-30 15:56 -------
Created an attachment (id=10081)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=10081&action=view)
Long test case directly from Linux kernel, shows the error in more
circumstances
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24585
next prev parent reply other threads:[~2005-10-30 15:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-30 15:55 [Bug target/24585] New: " ak at muc dot de
2005-10-30 15:56 ` ak at muc dot de [this message]
2005-10-30 16:12 ` [Bug target/24585] " pluto at agmk dot net
2005-10-30 16:13 ` [Bug middle-end/24585] [3.4/4.0/4.1 Regression] " pinskia at gcc dot gnu dot org
2005-10-30 16:18 ` pinskia at gcc dot gnu dot org
2005-10-31 6:45 ` mmitchel at gcc dot gnu dot org
2005-11-01 6:38 ` wilson at gcc dot gnu dot org
2005-11-01 14:55 ` pinskia at gcc dot gnu dot 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=20051030155645.17465.qmail@sourceware.org \
--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).