public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sje at cup dot hp.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/48209] FAIL: gcc.c-torture/execute/pr47917.c execution
Date: Mon, 21 Mar 2011 21:49:00 -0000 [thread overview]
Message-ID: <bug-48209-4-66gMFEKEHq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48209-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48209
Steve Ellcey <sje at cup dot hp.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sje at cup dot hp.com
--- Comment #2 from Steve Ellcey <sje at cup dot hp.com> 2011-03-21 21:42:02 UTC ---
It looks like this is broken for HP-UX 11.11 and 11.23. On 11.31 there is a
object that can be linked in (unix2003.o) to fix this. Just like we currently
link in unix95.0 or unix98.o for UNIX 1995 or UNIX 1998 standards, if you link
in unix2003.o then you will get the UNIX 2003 standard and the correct C99
handling of snprintf.
next prev parent reply other threads:[~2011-03-21 21:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-20 15:23 [Bug middle-end/48209] New: " danglin at gcc dot gnu.org
2011-03-20 19:38 ` [Bug middle-end/48209] " jakub at gcc dot gnu.org
2011-03-21 21:49 ` sje at cup dot hp.com [this message]
2011-03-22 0:30 ` [Bug target/48209] " dave at hiauly1 dot hia.nrc.ca
2011-03-22 16:57 ` sje at cup dot hp.com
2011-03-22 17:05 ` jakub at gcc dot gnu.org
2011-03-22 17:13 ` sje at cup dot hp.com
2011-03-22 17:59 ` jakub at gcc dot gnu.org
2011-03-22 18:51 ` sje at cup dot hp.com
2011-03-22 20:07 ` dave at hiauly1 dot hia.nrc.ca
2011-03-22 20:16 ` sje at cup dot hp.com
2011-03-22 22:06 ` dave at hiauly1 dot hia.nrc.ca
2011-03-24 16:43 ` sje at gcc dot gnu.org
2011-03-24 16:54 ` sje at cup dot hp.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=bug-48209-4-66gMFEKEHq@http.gcc.gnu.org/bugzilla/ \
--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).