From: Roland McGrath <roland@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: [PATCH] Re: bswap on prescott
Date: Thu, 25 Jan 2007 01:23:00 -0000 [thread overview]
Message-ID: <20070125012253.998341800E9@magilla.sf.frob.com> (raw)
In-Reply-To: Jakub Jelinek's message of Wednesday, 24 January 2007 22:54:14 +0100 <20070124215414.GM3819@sunsite.mff.cuni.cz>
It really would be more reasonable if GCC defined some things meaning "this
or later" or "has these features", so that things like this don't have to
change every year to still mean ">= i486".
prev parent reply other threads:[~2007-01-25 1:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4354d3270701241326v596084d5m2341d6ce2cfa201f@mail.gmail.com>
2007-01-24 21:51 ` Jakub Jelinek
2007-01-25 1:23 ` Roland McGrath [this message]
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=20070125012253.998341800E9@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=jakub@redhat.com \
--cc=libc-hacker@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).