public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/48620] many libstdc++ tests FAIL with -m32 -fno-early-inlining -fipa-pta
Date: Thu, 02 Apr 2015 12:57:00 -0000 [thread overview]
Message-ID: <bug-48620-4-gFS6Uu47Kz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48620-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48620
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jens Breitbart from comment #2)
> Created attachment 35213 [details]
> Add _mask_range_hashing to hashtable_policy.h v1
Jens, I think you meant to attach this to PR65641, but as I said there, unless
you have a copyright assignment we can't use it anyway.
next prev parent reply other threads:[~2015-04-02 12:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-15 12:49 [Bug tree-optimization/48620] New: " zsojka at seznam dot cz
2011-04-15 12:53 ` [Bug tree-optimization/48620] " rguenth at gcc dot gnu.org
2015-04-02 12:37 ` j.breitbart at tum dot de
2015-04-02 12:57 ` redi at gcc dot gnu.org [this message]
2015-04-02 13:09 ` j.breitbart at tum dot de
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-48620-4-gFS6Uu47Kz@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).