public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug optimization/7871] [3.3/3.4 regression] ICE on legal code, global register variables problems
Date: Sun, 11 Jan 2004 13:09:00 -0000 [thread overview]
Message-ID: <20040111130949.15688.qmail@sources.redhat.com> (raw)
In-Reply-To: <20020909143600.7871.rz@linux-m68k.org>
------- Additional Comments From ebotcazou at gcc dot gnu dot org 2004-01-11 13:09 -------
Yes, the global register variable extension is broken in GCC 3.x (possibly not
in GCC 3.0.x, but those releases were barely usable anyway).
Jim, you could perhaps bring the issue to the SC so that we have a definitive
position: either it is still supported and it must be given top priority for 3.4
or it is removed.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7871
next prev parent reply other threads:[~2004-01-11 13:09 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020909143600.7871.rz@linux-m68k.org>
2003-08-20 4:17 ` [Bug c/7871] " pinskia at gcc dot gnu dot org
2003-08-29 18:04 ` [Bug target/7871] [3.3/3.4 regression] " bangerth at dealii dot org
2004-01-11 0:45 ` [Bug optimization/7871] " pinskia at gcc dot gnu dot org
2004-01-11 11:54 ` rz at linux-m68k dot org
2004-01-11 13:09 ` ebotcazou at gcc dot gnu dot org [this message]
2004-01-11 16:39 ` simonmar at microsoft dot com
2004-01-11 17:54 ` rz at linux-m68k dot org
2004-01-11 17:59 ` rz at linux-m68k dot org
2004-01-11 20:10 ` rth at redhat dot com
2004-01-12 9:54 ` simonmar at microsoft dot com
2004-01-12 23:39 ` steven at gcc dot gnu dot org
2004-01-14 17:45 ` simonmar at microsoft dot com
2004-01-14 17:49 ` pinskia at gcc dot gnu dot org
2004-02-03 7:46 ` [Bug optimization/7871] [3.3/3.4/3.5 " ebotcazou at gcc dot gnu dot org
2004-02-12 16:34 ` ian at wasabisystems dot com
2004-02-13 11:41 ` rz at linux-m68k dot org
2004-02-13 12:24 ` simonmar at microsoft dot com
2004-02-16 3:15 ` giovannibajo at libero dot it
2004-02-16 14:32 ` uweigand at gcc dot gnu dot org
2004-02-17 10:20 ` giovannibajo at libero dot it
2004-02-17 10:24 ` simonmar at microsoft dot com
2004-02-17 16:00 ` simonmar at microsoft dot com
2004-02-17 17:03 ` simonmar at microsoft dot com
2004-02-17 17:41 ` giovannibajo at libero dot it
2004-02-17 18:07 ` ebotcazou at gcc dot gnu dot org
2004-02-18 8:49 ` wilson at gcc dot gnu dot org
2004-02-18 9:06 ` giovannibajo at libero dot it
2004-02-18 9:13 ` wilson at specifixinc dot com
2004-02-27 9:21 ` ian at wasabisystems dot com
2004-02-27 13:19 ` rz at linux-m68k dot org
2004-02-28 2:43 ` cvs-commit at gcc dot gnu dot org
2004-02-28 2:45 ` [Bug optimization/7871] [3.3/3.4 " ian at wasabisystems dot com
2004-02-28 3:39 ` cvs-commit at gcc dot gnu dot org
2004-02-28 3:40 ` [Bug optimization/7871] [3.3 " ian at wasabisystems dot com
2004-02-28 13:36 ` cvs-commit at gcc dot gnu dot org
2004-02-28 13:38 ` ian at wasabisystems dot com
2004-03-08 10:17 ` cvs-commit at gcc dot gnu dot org
2004-04-13 11:26 ` pinskia at gcc dot gnu dot org
2004-04-13 12:32 ` 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=20040111130949.15688.qmail@sources.redhat.com \
--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).