public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/54402] [4.8 Regression] var-tracking does not scale
Date: Wed, 12 Dec 2012 11:07:00 -0000 [thread overview]
Message-ID: <bug-54402-4-Oncu9jHGpi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54402-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54402
--- Comment #19 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> 2012-12-12 11:07:21 UTC ---
> --- Comment #18 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-12-10
> 10:56:51 UTC ---
> (In reply to comment #16)
>> Not on Solaris/SPARC, unfortunately: there are still compilations in the
>> libgo testsuite that take more than a day, which with PR go/54507
>> effectivly breaks unattended Solaris/SPARC bootstraps since they take
>> insanely long.
>
> Which exact testcase? Can you pin-point it to a single *.go source file
> compilation rather than several as the libgo testsuite usually compiles?
> Can you see what all files would need to be attached to make it reproduceable
> using cross-compiler from say x86_64-linux? I bet some *.gox files would be
> needed...
One example is reflect-check. It doesn't work with a single *.go file,
but two do the trick. With -fno-var-tracking-assignements, it takes
3:41 on a 1.2 GHz UltraSPARC-T2, without it's on the order of a day.
I'm attaching a tarball with all the files necessary to reproduce with a
native sparc-sun-solaris2.10 compiler, including reflect.sh with the
exact go1 invocation. Haven't tried a cross yet.
Rainer
next prev parent reply other threads:[~2012-12-12 11:07 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-29 9:48 [Bug debug/54402] New: " steven at gcc dot gnu.org
2012-08-29 9:50 ` [Bug debug/54402] " steven at gcc dot gnu.org
2012-09-03 10:13 ` rguenth at gcc dot gnu.org
2012-10-05 17:57 ` markus at trippelsdorf dot de
2012-10-16 14:42 ` markus at trippelsdorf dot de
2012-10-16 18:38 ` markus at trippelsdorf dot de
2012-10-26 10:53 ` rsandifo at gcc dot gnu.org
2012-10-26 23:07 ` vmakarov at redhat dot com
2012-10-27 7:24 ` ubizjak at gmail dot com
2012-10-29 9:49 ` jakub at gcc dot gnu.org
2012-10-29 17:14 ` jakub at gcc dot gnu.org
2012-10-29 17:24 ` jakub at gcc dot gnu.org
2012-10-30 10:59 ` markus at trippelsdorf dot de
2012-10-30 11:25 ` markus at trippelsdorf dot de
2012-10-30 12:26 ` markus at trippelsdorf dot de
2012-10-30 18:24 ` jakub at gcc dot gnu.org
2012-11-05 7:59 ` jakub at gcc dot gnu.org
2012-12-06 16:42 ` rguenth at gcc dot gnu.org
2012-12-06 16:57 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-12-06 17:01 ` jakub at gcc dot gnu.org
2012-12-10 10:57 ` jakub at gcc dot gnu.org
2012-12-12 11:07 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
2012-12-12 11:10 ` ro at gcc dot gnu.org
2012-12-12 22:10 ` jakub at gcc dot gnu.org
2012-12-12 22:22 ` jakub at gcc dot gnu.org
2012-12-12 22:30 ` jakub at gcc dot gnu.org
2012-12-13 13:12 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-12-24 0:37 ` jan.smets@alcatel-lucent.com
2013-01-03 8:52 ` jakub at gcc dot gnu.org
2013-01-18 11:01 ` aoliva at gcc dot gnu.org
2013-01-18 11:08 ` aoliva at gcc dot gnu.org
2013-01-21 10:07 ` ro at CeBiTec dot Uni-Bielefeld.DE
2013-01-23 16:49 ` rguenth at gcc dot gnu.org
2013-01-24 12:46 ` ro at CeBiTec dot Uni-Bielefeld.DE
2013-03-22 14:43 ` [Bug debug/54402] [4.8/4.9 " jakub at gcc dot gnu.org
2013-05-31 10:57 ` jakub at gcc dot gnu.org
2013-10-16 9:50 ` jakub at gcc dot gnu.org
2013-10-25 11:20 ` rguenth at gcc dot gnu.org
2013-10-25 11:48 ` rguenth 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-54402-4-Oncu9jHGpi@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).