public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug regression/62102] [5 Regression]: gcc.dg/torture/pr48953.c -O2 -flto
Date: Tue, 14 Oct 2014 06:45:00 -0000 [thread overview]
Message-ID: <bug-62102-4-6kezCBMwoC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-62102-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62102
--- Comment #8 from Jan Hubicka <hubicka at ucw dot cz> ---
>
> My autotester picked up that commit, and this regression is gone, thanks!
> I'm closing this PR.
Great! I was starring in that patch and did not notice this quite obvious
omision
for at least 20 times :( Good it is gone.
The consequences of not remapping the type were particularly confusing to deal
with...
Honza
>
> Specifically, this regression is gone with a commit in the range
> (216146:216158], matching the commit in question. Incidentally, at r216158
> there's only gcc.dg/tls/alias-1.c i.e. PR61548 (since I started tracking
> regressions for cris-elf in 2007).
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
prev parent reply other threads:[~2014-10-14 6:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 2:01 [Bug regression/62102] New: [4.10 " hp at gcc dot gnu.org
2014-08-13 8:29 ` [Bug regression/62102] " rguenth at gcc dot gnu.org
2014-08-13 17:13 ` [Bug regression/62102] [5 " hubicka at gcc dot gnu.org
2014-08-13 17:17 ` hubicka at gcc dot gnu.org
2014-08-13 22:28 ` hp at gcc dot gnu.org
2014-09-19 21:45 ` hubicka at gcc dot gnu.org
2014-10-13 14:47 ` hubicka at gcc dot gnu.org
2014-10-14 0:46 ` hp at gcc dot gnu.org
2014-10-14 6:45 ` hubicka at ucw dot cz [this message]
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-62102-4-6kezCBMwoC@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).