public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "phil at fsel dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/14962] [3.3/3.4/3.5 regression] g++ ignores #pragma redefine_extname
Date: Tue, 04 May 2004 14:06:00 -0000	[thread overview]
Message-ID: <20040504140600.26842.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040415092711.14962.phil@fsel.com>


------- Additional Comments From phil at fsel dot com  2004-05-04 14:05 -------
You're quite right. I thought I'd tested it with g++, but obviously I hadn't.
Should have kept a table of all the combinations of code and compiler I'd tried...



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14962


  parent reply	other threads:[~2004-05-04 14:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-15  9:30 [Bug c++/14962] New: g++ appears to ignore #pragma redirect_extname phil at fsel dot com
2004-04-15  9:41 ` [Bug c++/14962] " phil at fsel dot com
2004-04-15  9:45 ` phil at fsel dot com
2004-04-15  9:55 ` phil at fsel dot com
2004-04-15 11:05 ` phil at fsel dot com
2004-04-15 11:55 ` phil at fsel dot com
2004-04-15 12:12 ` ebotcazou at gcc dot gnu dot org
2004-04-15 13:47 ` phil at fsel dot com
2004-04-20 12:48 ` [Bug c++/14962] g++ ignores " ebotcazou at gcc dot gnu dot org
2004-04-20 13:05 ` phil at fsel dot com
2004-04-20 13:35 ` ebotcazou at gcc dot gnu dot org
2004-04-20 13:48 ` phil at fsel dot com
2004-04-20 13:50 ` [Bug c++/14962] [3.3/3.4 regression] g++ ignores #pragma redefine_extname ebotcazou at gcc dot gnu dot org
2004-04-20 15:10 ` phil at fsel dot com
2004-04-20 16:25 ` phil at fsel dot com
2004-05-04  8:06 ` [Bug c++/14962] [3.3/3.4/3.5 " ebotcazou at gcc dot gnu dot org
2004-05-04 12:14 ` ebotcazou at gcc dot gnu dot org
2004-05-04 14:06 ` phil at fsel dot com [this message]
2004-05-07  6:58 ` cvs-commit at gcc dot gnu dot org
2004-05-07  7:07 ` cvs-commit at gcc dot gnu dot org
2004-05-07  7:23 ` ebotcazou at gcc dot gnu dot org
2004-05-13  4:41 ` phil at fsel dot com

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=20040504140600.26842.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).