public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "scovich at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/34115] atomic builtins not supported on i686?
Date: Wed, 28 Nov 2007 14:20:00 -0000 [thread overview]
Message-ID: <20071128142042.10829.qmail@sourceware.org> (raw)
In-Reply-To: <bug-34115-14600@http.gcc.gnu.org/bugzilla/>
------- Comment #9 from scovich at gmail dot com 2007-11-28 14:20 -------
(In reply to comment #8)
> (In reply to comment #7)
> > Too bad they aren't defined for any machine I've tried so far...
>
> The explanation is very simple: the new macros are implemented only in mainline
> (would be 4.3.0).
>
Any chance of backporting? (I know, probably not)
The only question left is whether the compiler is supposed to emit a warning
when it doesn't support the intrinsics (like the docs say) or whether the user
should just be ready for linker errors.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34115
next prev parent reply other threads:[~2007-11-28 14:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-15 22:15 [Bug c/34115] New: " scovich at gmail dot com
2007-11-15 22:19 ` [Bug target/34115] " pinskia at gcc dot gnu dot org
2007-11-15 22:30 ` pcarlini at suse dot de
2007-11-15 23:53 ` joseph at codesourcery dot com
2007-11-16 0:07 ` pcarlini at suse dot de
2007-11-16 1:00 ` scovich at gmail dot com
2007-11-16 1:04 ` scovich at gmail dot com
2007-11-28 1:56 ` scovich at gmail dot com
2007-11-28 2:05 ` pcarlini at suse dot de
2007-11-28 14:20 ` scovich at gmail dot com [this message]
2009-06-08 21:18 ` joseph dot h dot garvin at gmail dot com
[not found] <bug-34115-4@http.gcc.gnu.org/bugzilla/>
2010-10-15 20:48 ` redi at gcc dot gnu.org
2021-09-12 8:16 ` pinskia at gcc dot gnu.org
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=20071128142042.10829.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).