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 fortran/45636] Failed to fold simple Fortran string
Date: Fri, 05 Nov 2010 21:13:00 -0000 [thread overview]
Message-ID: <bug-45636-4-xRSqchzUVi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-45636-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45636
Steve Ellcey <sje at cup dot hp.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sje at cup dot hp.com
--- Comment #13 from Steve Ellcey <sje at cup dot hp.com> 2010-11-05 21:12:19 UTC ---
I have moved gcc.c-torture/execute/pr45636.c to gcc.dg/torture/pr45636.c
and added a check for the mempcpy function so this should not fail on HP-UX or
Solaris which don't have a mempcpy function.
The change was r166378 and if the test failures are the only reason to keep
this bug report open then it we should be able to close it now.
next prev parent reply other threads:[~2010-11-05 21:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-45636-4@http.gcc.gnu.org/bugzilla/>
2010-09-27 11:07 ` tkoenig at gcc dot gnu.org
2010-10-12 22:01 ` jakub at gcc dot gnu.org
2010-10-16 18:59 ` danglin at gcc dot gnu.org
2010-10-17 15:42 ` dave at hiauly1 dot hia.nrc.ca
2010-10-28 17:54 ` ro at gcc dot gnu.org
2010-11-05 21:13 ` sje at cup dot hp.com [this message]
2010-11-07 7:46 ` burnus at gcc dot gnu.org
2010-11-07 19:44 ` dave at hiauly1 dot hia.nrc.ca
2010-11-08 16:08 ` sje at cup dot hp.com
2010-11-23 23:53 ` danglin at gcc dot gnu.org
2010-11-24 1:09 ` danglin at gcc dot gnu.org
2010-09-10 14:48 [Bug fortran/45636] New: " hjl dot tools at gmail dot com
2010-09-10 15:12 ` [Bug fortran/45636] " kargl at gcc dot gnu dot org
2010-09-10 15:20 ` kargl at gcc dot gnu dot org
2010-09-10 15:33 ` hjl dot tools at gmail dot com
2010-09-10 15:34 ` kargl at gcc dot gnu dot org
2010-09-10 15:47 ` jakub at gcc dot gnu dot 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=bug-45636-4-xRSqchzUVi@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).