public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "matoro_gcc_bugzilla at matoro dot tk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/106966] [12/13/14 Regression] alpha cross build crashes gcc-12 "internal compiler error: in emit_move_insn"
Date: Mon, 10 Jul 2023 14:41:17 +0000 [thread overview]
Message-ID: <bug-106966-4-BHbu3CKxYI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106966-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106966
--- Comment #11 from matoro <matoro_gcc_bugzilla at matoro dot tk> ---
(In reply to Uroš Bizjak from comment #10)
> (In reply to matoro from comment #9)
> > (In reply to Uroš Bizjak from comment #8)
> > > Created attachment 55504 [details]
> > > Proposed patch.
> > >
> > > Can someone please bootstrap and test the attached patch?
> >
> > I can queue this up to test on real hardware. By bootstrap, do you mean
> > with --enable-bootstrap, and by test do you mean a full testsuite run or
> > just checking that it doesn't ICE on the reproducer here?
>
> I have already checked that it doesn't ICE with a crosscompiler. Regarding
> the bootstrap, please note that --enable-bootstrap is the default nowadays,
> so the option it is not needed to make a full build ("bootstrap"). Also,
> "make -j N -k check-gcc" should be enough to test the compiler, since other
> parts of the compiler never exercise -mbuild-constants (N in the command
> should be substituted with a number of processors to parallelize the
> testsuite run).
I was just checking because alpha hardware is quite antique, it's single-core
so a full compile with bootstrap takes around ~72 hours. I don't know how long
the test suite takes because I've never run it on this machine, but I would
expect it to add a couple additional days to that. If that's fine I'll kick it
off, just want to be clear on what exactly you'd like to see.
next prev parent reply other threads:[~2023-07-10 14:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 10:56 [Bug c/106966] New: " christian.ehrhardt at canonical dot com
2022-09-19 11:11 ` [Bug c/106966] " christian.ehrhardt at canonical dot com
2022-09-19 13:49 ` [Bug target/106966] " ubizjak at gmail dot com
2022-09-19 14:15 ` christian.ehrhardt at canonical dot com
2022-09-20 7:19 ` ubizjak at gmail dot com
2022-09-22 6:30 ` christian.ehrhardt at canonical dot com
2022-09-23 8:20 ` ubizjak at gmail dot com
2023-07-08 12:11 ` ubizjak at gmail dot com
2023-07-08 13:47 ` ubizjak at gmail dot com
2023-07-08 13:50 ` [Bug target/106966] [12/13/14 Regression] " ubizjak at gmail dot com
2023-07-10 3:58 ` matoro_gcc_bugzilla at matoro dot tk
2023-07-10 6:32 ` ubizjak at gmail dot com
2023-07-10 14:41 ` matoro_gcc_bugzilla at matoro dot tk [this message]
2023-07-10 15:05 ` doko at gcc dot gnu.org
2023-07-13 13:19 ` doko at gcc dot gnu.org
2023-07-13 16:32 ` cvs-commit at gcc dot gnu.org
2023-07-13 16:34 ` cvs-commit at gcc dot gnu.org
2023-07-13 16:34 ` cvs-commit at gcc dot gnu.org
2023-07-13 16:37 ` ubizjak 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-106966-4-BHbu3CKxYI@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).