From: Eli Zaretskii <eliz@gnu.org>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: PATCH: Add x86 AVX XML files
Date: Tue, 02 Mar 2010 18:00:00 -0000 [thread overview]
Message-ID: <837hpu4n9h.fsf@gnu.org> (raw)
In-Reply-To: <20100302152128.GA28089@intel.com>
> Date: Tue, 2 Mar 2010 07:21:28 -0800
> From: "H.J. Lu" <hongjiu.lu@intel.com>
>
> I am submitting AVX patches in pieces since AVX changes are quite
> large. This patch adds x86 AVX target descriptions. OK to install?
Could you please add the necessary file-name mappings to
config/djgpp/fnchange.lst? Some of the new files will have their
names clash under the 8+3 DOS butchery. (You can use `doschk' to see
which files fall victim to this.)
Thanks.
next prev parent reply other threads:[~2010-03-02 18:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 15:21 H.J. Lu
2010-03-02 18:00 ` Eli Zaretskii [this message]
2010-03-02 19:16 ` H.J. Lu
2010-03-02 20:24 ` Eli Zaretskii
2010-03-02 21:05 ` H.J. Lu
2010-03-02 21:40 ` Eli Zaretskii
2010-03-02 23:10 ` Mark Kettenis
2010-03-03 0:01 ` H.J. Lu
2010-03-03 23:20 ` Mark Kettenis
2010-03-03 23:34 ` H.J. Lu
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=837hpu4n9h.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=hjl.tools@gmail.com \
/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