public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug optimization/192] String literals don't obey -fdata-sections Date: Sun, 17 Aug 2003 01:36:00 -0000 [thread overview] Message-ID: <20030817013627.30580.qmail@sources.redhat.com> (raw) In-Reply-To: <20000502194601.192.greyham@research.canon.com.au> PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=192 pinskia at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |enhancement
next prev parent reply other threads:[~2003-08-17 1:36 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20000502194601.192.greyham@research.canon.com.au> 2003-06-09 19:38 ` pinskia@physics.uc.edu 2003-08-17 1:36 ` pinskia at gcc dot gnu dot org [this message] 2004-05-23 20:28 ` [Bug rtl-optimization/192] " pinskia at gcc dot gnu dot org 2004-05-23 21:09 ` jsm at polyomino dot org dot uk 2004-05-23 23:12 ` giovannibajo at libero dot it 2004-05-24 2:38 ` [Bug middle-end/192] " pinskia at gcc dot gnu dot org 2004-10-13 13:40 ` pinskia at gcc dot gnu dot org 2004-11-30 6:36 ` amodra at bigpond dot net dot au
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=20030817013627.30580.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: linkBe 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).