public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/15486] [3.3/3.4/3.5] -fdata-sections moves common vars to .bss
Date: Tue, 22 Jun 2004 11:33:00 -0000 [thread overview]
Message-ID: <20040622113337.27791.qmail@sourceware.org> (raw)
In-Reply-To: <20040517064727.15486.jifl-bugzilla@jifvik.org>
------- Additional Comments From rearnsha at gcc dot gnu dot org 2004-06-22 11:33 -------
Just because the compiler changed behaviour doesn't necessarily make it a
regression. Perhaps the change was intentional.
It could be equally argued that failing to put uninitialized data in separate
sections was the bug that was being fixed when the change was introduced. It
would be necessary to do some archeology to find out which patch caused the
change, and why it was proposed in the first place.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15486
next prev parent reply other threads:[~2004-06-22 11:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-17 19:32 [Bug target/15486] New: -fdata-sections moves COMMON " jifl-bugzilla at jifvik dot org
2004-05-17 21:59 ` [Bug middle-end/15486] " pinskia at gcc dot gnu dot org
2004-05-17 22:03 ` jifl-bugzilla at jifvik dot org
2004-05-17 22:04 ` ebotcazou at gcc dot gnu dot org
2004-05-17 22:05 ` [Bug middle-end/15486] [3.3/3.4/3.5] -fdata-sections moves common " ebotcazou at gcc dot gnu dot org
2004-05-18 14:17 ` jifl-bugzilla at jifvik dot org
2004-06-06 3:58 ` giovannibajo at libero dot it
2004-06-19 17:46 ` mmitchel at gcc dot gnu dot org
2004-06-22 10:26 ` rearnsha at gcc dot gnu dot org
2004-06-22 11:12 ` jifl-bugzilla at jifvik dot org
2004-06-22 11:33 ` rearnsha at gcc dot gnu dot org [this message]
2004-06-22 19:37 ` jifl-bugzilla at jifvik dot org
2004-06-22 22:13 ` jifl-bugzilla at jifvik dot org
2004-08-17 23:17 ` pinskia at gcc dot gnu dot org
2004-08-18 1:39 ` jifl-bugzilla at jifvik dot org
2004-08-18 2:22 ` pinskia at gcc dot gnu dot org
2004-08-18 4:42 ` jifl-bugzilla at jifvik dot org
2004-08-19 21:18 ` mmitchel at gcc dot gnu dot org
2004-08-20 21:09 ` jason at redhat dot com
2004-08-29 19:09 ` mmitchel at gcc dot gnu dot org
2004-10-13 13:42 ` [Bug middle-end/15486] [3.3/3.4/4.0 regression] " pinskia at gcc dot gnu dot org
2004-10-31 2:07 ` mmitchel at gcc dot gnu dot org
2004-12-09 13:16 ` ebotcazou at gcc dot gnu dot org
2004-12-14 8:22 ` ebotcazou at gcc dot gnu dot org
2004-12-18 21:50 ` cvs-commit at gcc dot gnu dot org
2004-12-18 21:56 ` ebotcazou 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=20040622113337.27791.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).