public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "markus at trippelsdorf dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/49533] [4.7 regression] Revision 174989 (ipa-inline-transform.c)  regressions
Date: Mon, 11 Jul 2011 19:45:00 -0000	[thread overview]
Message-ID: <bug-49533-4-0ijhMA90U0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49533-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49533

Markus Trippelsdorf <markus at trippelsdorf dot de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[4.7 regression] Firefox    |[4.7 regression] Revision
                   |profiled build issues       |174989
                   |                            |(ipa-inline-transform.c)
                   |                            |regressions

--- Comment #7 from Markus Trippelsdorf <markus at trippelsdorf dot de> 2011-07-11 19:45:06 UTC ---
Another instance of the same regression (caused by commit 7791b0eb56c3c):

stellarium build (without PGO) with latest gcc crashes on exit:

[Thread 0x7fffee9cb700 (LWP 16857) exited]
[Thread 0x7ffff4d5a700 (LWP 16821) exited]

Program received signal SIGSEGV, Segmentation fault.
0x0000000000000000 in ?? ()
(gdb) bt
#0  0x0000000000000000 in ?? ()
#1  0x00007ffff6c331b1 in __run_exit_handlers (status=0, listp=0x7ffff6d594c8,
run_list_atexit=true) at exit.c:78
#2  0x00007ffff6c33235 in exit (status=Unhandled dwarf expression opcode 0xf3
) at exit.c:100
#3  0x00007ffff6c1cf89 in __libc_start_main (main=0x60b500 <main>, argc=1,
ubp_av=0x7fffffffe158, init=Unhandled dwarf expression opcode 0xf3
) at libc-start.c:258
#4  0x00000000004a2589 in _start ()

Reverting 7791b0eb56c3c "solves" the problem.

And I guess Bug 49665 is a dup of the same issue.


  parent reply	other threads:[~2011-07-11 19:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-26 19:47 [Bug other/49533] New: Firefox profiled build issues markus at trippelsdorf dot de
2011-06-27 10:14 ` [Bug other/49533] " hubicka at gcc dot gnu.org
2011-06-27 10:25 ` markus at trippelsdorf dot de
2011-06-27 10:53 ` hubicka at ucw dot cz
2011-06-28 14:51 ` markus at trippelsdorf dot de
2011-07-07 16:21 ` [Bug other/49533] [4.7 regression] " markus at trippelsdorf dot de
2011-07-07 20:30 ` markus at trippelsdorf dot de
2011-07-11 19:45 ` markus at trippelsdorf dot de [this message]
2011-07-13 21:14 ` [Bug other/49533] [4.7 regression] Revision 174989 (ipa-inline-transform.c) regressions markus at trippelsdorf dot de
2011-08-01 14:31 ` rguenth at gcc dot gnu.org
2011-08-31 21:47 ` pinskia at gcc dot gnu.org
2011-09-01  6:44 ` markus at trippelsdorf dot de
2011-09-13 10:15 ` hubicka at gcc dot gnu.org
2011-09-13 10:15 ` hubicka at gcc dot gnu.org
2011-09-13 12:31 ` markus at trippelsdorf dot de
2011-09-13 14:40 ` hubicka at gcc dot gnu.org
2011-09-13 15:04 ` hubicka at gcc dot gnu.org
2011-09-14 18:29 ` d.g.gorbachev at gmail 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=bug-49533-4-0ijhMA90U0@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).