public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gary at intrepid dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/67000] [6 Regression] ICE in split_complex_args, at function.c:2325 on ppc64le
Date: Thu, 30 Jul 2015 20:00:00 -0000 [thread overview]
Message-ID: <bug-67000-4-wL8rWdQGdW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67000-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67000
--- Comment #4 from Gary Funck <gary at intrepid dot com> ---
(In reply to Alexandre Oliva from comment #3)
> The problem initially reported in this bug is now fixed in the git branch
> aoliva/pr64164. I'm not sure how to go about duplicating the one in comment
> 1, but, having fixed a number of additional split_complex issues since the
> patch that caused the problems was put in, I hope it's fixed too. Gary,
> would you please detail the toplevel configure and build command lines to
> trigger it, or perhaps give the branch a try and confirm that it fixes the
> problem? Thanks,
Alexandre,
The configuration command was along these lines:
configure CFLAGS='-g3 -O0' CXXFLAGS='-g3 -O0' TARGET_CFLAGS='-g3 -O0'
TARGET_CXXFLAGS='-g3 -O0' --enable-bootstrap=no --enable-checking=yes
--enable-languages=c,c++ --disable-build-format-warnings
PS: the issue did go away when merged with a later svn trunk version,
consistent with Richard's comment #2.
next prev parent reply other threads:[~2015-07-30 20:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-24 18:21 [Bug rtl-optimization/67000] New: " redi at gcc dot gnu.org
2015-07-26 16:52 ` [Bug rtl-optimization/67000] " gary at intrepid dot com
2015-07-27 8:18 ` rguenth at gcc dot gnu.org
2015-07-30 20:00 ` gary at intrepid dot com [this message]
2015-08-14 18:52 ` aoliva at gcc dot gnu.org
2015-08-15 2:26 ` aoliva at gcc dot gnu.org
2015-08-21 20:05 ` aoliva 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-67000-4-wL8rWdQGdW@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).