public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikulas at artax dot karlin.mff.cuni.cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/52778] gcc crashes with -flto on PA-RISC
Date: Thu, 29 Mar 2012 18:26:00 -0000	[thread overview]
Message-ID: <bug-52778-4-uuwBh9bSZ0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52778-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from mikulas at artax dot karlin.mff.cuni.cz 2012-03-29 18:25:43 UTC ---
I couldn't attach the file, so I placed in on
http://jikos.cz/~mikulas/gcc-crash-files.tar.bz2 . Download the archive, change
CC in the Makefile to point to your gcc-4.7.0 PA-RISC binary and run make. This
will reproduce the gcc crash.


  reply	other threads:[~2012-03-29 18:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-29 18:21 [Bug lto/52778] New: " mikulas at artax dot karlin.mff.cuni.cz
2012-03-29 18:26 ` mikulas at artax dot karlin.mff.cuni.cz [this message]
2012-03-29 18:30 ` [Bug lto/52778] " mikulas at artax dot karlin.mff.cuni.cz
2012-03-29 19:02 ` mikulas at artax dot karlin.mff.cuni.cz
2012-05-07 13:18 ` rguenth at gcc dot gnu.org
2012-12-23  4:05 ` danglin at gcc dot gnu.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-52778-4-uuwBh9bSZ0@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).