From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] new ".serialize" gas directive
Date: Fri, 14 May 2004 18:30:40 +0000 [thread overview]
Message-ID: <16549.4176.858082.629501@napali.hpl.hp.com> (raw)
In-Reply-To: <16537.51724.854691.934006@napali.hpl.hp.com>
>>>>> On 14 May 2004 01:43:55 -0700, Jim Wilson <wilson@specifixinc.com> said:
Jim> I think that is a reasonable bug report, especially considering
Jim> how close we are now to getting this right. Having a bug
Jim> report for it will be easier for me to track than an email
Jim> message in a folder I never look at.
I see. So I went ahead and put it in bugzilla (see
http://gcc.gnu.org/bugzilla/show_bug.cgi?id\x15445).
Thanks,
--david
next prev parent reply other threads:[~2004-05-14 18:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-06 5:15 [PATCH] new ".serialize" gas directive David Mosberger
2004-05-06 23:33 ` Jim Wilson
2004-05-06 23:47 ` David Mosberger
2004-05-07 7:48 ` Jim Wilson
2004-05-10 20:16 ` David Mosberger
2004-05-14 8:43 ` Jim Wilson
2004-05-14 18:30 ` David Mosberger [this message]
2004-06-16 1:54 ` Chris Wedgwood
2004-06-16 21:57 ` Jim Wilson
2004-06-16 22:04 ` Chris Wedgwood
2004-06-16 22:42 ` Jim Wilson
2004-06-16 22:56 ` Luck, Tony
2004-06-16 23:01 ` David Mosberger
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=16549.4176.858082.629501@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@vger.kernel.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