public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld dot DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/45028] [4.6 regression] ICE building 64-bit libjava on Solaris 2/SPARC: output_operand: invalid expression as operand
Date: Thu, 22 Jul 2010 12:10:00 -0000 [thread overview]
Message-ID: <20100722121022.3860.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45028-279@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from ro at CeBiTec dot Uni-Bielefeld dot DE 2010-07-22 12:10 -------
Subject: Re: [4.6 regression] ICE building 64-bit libjava on Solaris 2/SPARC:
output_operand: invalid expression as operand
> ------- Comment #3 from jakub at gcc dot gnu dot org 2010-07-22 10:46 -------
> This one actually shouldn't be IMHO delegimized, the setm44 value is just a
> temporary and thus it shouldn't hold any value interesting for debug info.
> Can you please attach -fdump-rtl-vartrack dump?
Done. It took me some time because the files isn't created in the
working directory, but in the depths of gnu/javax/print/ipp/attribute ;-(
I had to run jc1 under truss to find it.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45028
next prev parent reply other threads:[~2010-07-22 12:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 10:10 [Bug bootstrap/45028] New: " ro at gcc dot gnu dot org
2010-07-22 10:23 ` [Bug bootstrap/45028] " jakub at gcc dot gnu dot org
2010-07-22 10:35 ` ro at CeBiTec dot Uni-Bielefeld dot DE
2010-07-22 10:47 ` jakub at gcc dot gnu dot org
2010-07-22 12:09 ` ro at gcc dot gnu dot org
2010-07-22 12:10 ` ro at CeBiTec dot Uni-Bielefeld dot DE [this message]
2010-07-22 13:02 ` jakub at gcc dot gnu dot org
2010-07-22 13:10 ` ro at gcc dot gnu dot org
2010-07-22 13:35 ` jakub at gcc dot gnu dot org
2010-07-22 13:50 ` ro at CeBiTec dot Uni-Bielefeld dot DE
2010-07-22 13:51 ` ro at gcc dot gnu dot org
2010-07-22 13:52 ` jakub at gcc dot gnu dot org
2010-07-22 13:54 ` ro at gcc dot gnu dot org
2010-07-22 14:03 ` jakub at gcc dot gnu dot org
2010-07-22 14:06 ` ro at gcc dot gnu dot org
2010-07-22 14:07 ` ro at gcc dot gnu dot org
2010-07-22 14:20 ` jakub at gcc dot gnu dot org
2010-07-22 14:29 ` ro at CeBiTec dot Uni-Bielefeld dot DE
2010-07-22 14:58 ` jakub at gcc dot gnu dot org
2010-07-22 15:05 ` ro at CeBiTec dot Uni-Bielefeld dot DE
2010-07-22 15:33 ` jakub at gcc dot gnu dot org
2010-07-22 15:54 ` ro at CeBiTec dot Uni-Bielefeld dot DE
2010-07-22 20:49 ` jakub at gcc dot gnu dot org
2010-07-23 8:59 ` ro at CeBiTec dot Uni-Bielefeld dot DE
2010-07-31 10:22 ` [Bug bootstrap/45028] [4.6 Regression] " rguenth at gcc dot gnu dot org
2010-08-25 9:54 ` 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=20100722121022.3860.qmail@sourceware.org \
--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).