public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zack at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/17982] stop calling assemble_external before final assembly output time
Date: Wed, 08 Dec 2004 22:04:00 -0000 [thread overview]
Message-ID: <20041208220439.16959.qmail@sourceware.org> (raw)
In-Reply-To: <20041013220543.17982.schwab@suse.de>
------- Additional Comments From zack at gcc dot gnu dot org 2004-12-08 22:04 -------
Uh, no, it's not fixed. It is, however, papered over adequately for 4.0. I'm
turning this into a 4.1 enhancement PR.
http://gcc.gnu.org/ml/gcc-patches/2004-12/msg00491.html explains what needs to
happen for 4.1.
--
What |Removed |Added
----------------------------------------------------------------------------
OtherBugsDependingO|18632 |
nThis| |
Severity|critical |enhancement
Status|RESOLVED |REOPENED
Keywords|patch, wrong-code |
Resolution|FIXED |
Summary|[4.0 regression] asm |stop calling
|declaration ignored due to |assemble_external before
|conflict with previous |final assembly output time
|rename |
Target Milestone|4.0.0 |4.1.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17982
next prev parent reply other threads:[~2004-12-08 22:04 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 22:05 [Bug target/17982] New: [4.0 regression] asm declaration ignored due to conflict with previous rename schwab at suse dot de
2004-10-13 23:03 ` [Bug target/17982] " pinskia at gcc dot gnu dot org
2004-10-13 23:04 ` pinskia at gcc dot gnu dot org
2004-10-13 23:18 ` pinskia at gcc dot gnu dot org
2004-10-13 23:22 ` pinskia at gcc dot gnu dot org
2004-10-13 23:29 ` zack at codesourcery dot com
2004-10-13 23:49 ` pinskia at gcc dot gnu dot org
2004-11-09 15:47 ` schwab at suse dot de
2004-11-23 19:13 ` hjl at lucon dot org
2004-11-23 19:18 ` hjl at lucon dot org
2004-11-23 19:22 ` [Bug middle-end/17982] " pinskia at gcc dot gnu dot org
2004-11-23 21:13 ` hjl at lucon dot org
2004-11-23 22:20 ` zack at codesourcery dot com
2004-11-23 23:42 ` hjl at lucon dot org
2004-11-24 2:01 ` hjl at lucon dot org
2004-11-27 0:30 ` neroden at gcc dot gnu dot org
2004-11-27 20:25 ` zack at codesourcery dot com
2004-11-27 20:45 ` hjl at lucon dot org
2004-11-28 20:16 ` zack at codesourcery dot com
2004-11-28 22:48 ` schwab at suse dot de
2004-11-29 16:38 ` zack at codesourcery dot com
2004-11-29 17:07 ` schwab at suse dot de
2004-11-29 17:15 ` zack at codesourcery dot com
2004-11-29 18:47 ` hjl at lucon dot org
2004-12-08 19:13 ` cvs-commit at gcc dot gnu dot org
2004-12-08 20:01 ` pinskia at gcc dot gnu dot org
2004-12-08 22:04 ` zack at gcc dot gnu dot org [this message]
2004-12-08 22:05 ` [Bug middle-end/17982] stop calling assemble_external before final assembly output time zack at gcc dot gnu dot org
2005-04-05 1:54 ` pinskia at gcc dot gnu dot org
2005-07-05 2:10 ` pinskia at gcc dot gnu dot org
[not found] <bug-17982-50@http.gcc.gnu.org/bugzilla/>
2006-12-12 3:59 ` hjl at gcc dot gnu dot org
2006-12-16 2:47 ` kazu at gcc dot gnu dot org
2008-11-24 4:33 ` hackbunny at reactos dot com
2008-11-24 4:34 ` hackbunny at reactos dot com
2008-11-24 6:42 ` dannysmith at users dot sourceforge dot net
2010-08-09 21:13 ` steven at gcc dot gnu dot org
2010-08-10 13:02 ` iains 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=20041208220439.16959.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).