From: Andreas Jaeger <aj@suse.de>
To: Roland McGrath <roland@redhat.com>
Cc: GNU libc hackers <libc-hacker@sources.redhat.com>
Subject: Re: Get rid of warning in linuxthreads/spinlock.c
Date: Fri, 23 Jan 2004 13:17:00 -0000 [thread overview]
Message-ID: <m3r7xq24ae.fsf@gromit.moeb> (raw)
In-Reply-To: <200401222312.i0MNCnqp029474@magilla.sf.frob.com> (Roland McGrath's message of "Thu, 22 Jan 2004 15:12:49 -0800")
[-- Attachment #1: Type: text/plain, Size: 559 bytes --]
Roland McGrath <roland@redhat.com> writes:
>>
>> this patch gets rid of:
>>
>> spinlock.c:33: warning: matching constraint does not allow a register
>>
>> Ok to commit?
>
> If using the "m" constraint works right in all gcc >= 3.2, then fine.
>
Yes, it should. I tested with 3.3 and AFAIK only the warning is
new...
Ok, will commit now,
Andreas
--
Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj
SuSE Linux AG, Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
prev parent reply other threads:[~2004-01-23 13:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 11:03 Andreas Jaeger
2004-01-22 23:12 ` Roland McGrath
2004-01-23 13:17 ` Andreas Jaeger [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=m3r7xq24ae.fsf@gromit.moeb \
--to=aj@suse.de \
--cc=libc-hacker@sources.redhat.com \
--cc=roland@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).