public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Dara Hazeghi <dhazeghi@yahoo.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: ada/9519: gnat-3.2: clash of assembler symbols for overloaded names
Date: Tue, 13 May 2003 00:36:00 -0000 [thread overview]
Message-ID: <20030513003602.9656.qmail@sources.redhat.com> (raw)
The following reply was made to PR ada/9519; it has been noted by GNATS.
From: Dara Hazeghi <dhazeghi@yahoo.com>
To: gcc-gnats@gcc.gnu.org, oliver.kellogg@sysde.eads.net, nobody@gcc.gnu.org
Cc:
Subject: Re: ada/9519: gnat-3.2: clash of assembler symbols for overloaded names
Date: Mon, 12 May 2003 17:32:31 -0700
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-
trail&database=gcc&pr=9519
Hello,
I was able to reproduce this problem on gcc 3.2, but on 3.3 branch and
mainline (20030510) on i686-linux, the testcase compiled an assembled
fine, so it appears that this bug has been fixed.
Dara
next reply other threads:[~2003-05-13 0:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 0:36 Dara Hazeghi [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-13 6:27 steven
2003-01-31 10:46 oliver.kellogg
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=20030513003602.9656.qmail@sources.redhat.com \
--to=dhazeghi@yahoo.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).