public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/33437] potentially valid construct rejected
Date: Sat, 15 Nov 2008 00:45:00 -0000 [thread overview]
Message-ID: <20081115004349.32702.qmail@sourceware.org> (raw)
In-Reply-To: <bug-33437-1068@http.gcc.gnu.org/bugzilla/>
------- Comment #1 from pinskia at gcc dot gnu dot org 2008-11-15 00:43 -------
This works for me with PPC both 32bit and 64bit but fails with 64bit i686 and
works with 32bit x86.
--
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Component|c |target
Ever Confirmed|0 |1
GCC build triplet|x86_64-linux-gnu |
GCC host triplet|x86_64-linux-gnu |
GCC target triplet|x86_64-linux-gnu |x86_64-*-*
Last reconfirmed|0000-00-00 00:00:00 |2008-11-15 00:43:49
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33437
next prev parent reply other threads:[~2008-11-15 0:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-14 15:25 [Bug c/33437] New: " jbeulich at novell dot com
2008-11-15 0:45 ` pinskia at gcc dot gnu dot org [this message]
[not found] <bug-33437-4@http.gcc.gnu.org/bugzilla/>
2021-08-09 4:58 ` [Bug target/33437] " pinskia at gcc dot gnu.org
2021-08-10 8:04 ` jbeulich at suse dot com
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=20081115004349.32702.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).