public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aldyh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/114985] [15 regression] internal compiler error: in discriminator_fail during stage2
Date: Thu, 16 May 2024 12:50:40 +0000	[thread overview]
Message-ID: <bug-114985-4-GWa3ilS8nR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114985-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114985

--- Comment #29 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
(In reply to ro@CeBiTec.Uni-Bielefeld.DE from comment #28)
> > --- Comment #27 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
> > This is in cfarm216.cfarm.et:
> >
> > aldyh@s11-sparc:~/bld/clean$ hostname
> > s11-sparc.cfarm
> > aldyh@s11-sparc:~/bld/clean$ uname -a
> > SunOS s11-sparc.cfarm 5.11 11.4.68.164.2 sun4v sparc sun4v logical-domain
> > aldyh@s11-sparc:~/bld/clean$ ~/src/clean/configure && gmake -j80 && gmake check
> > -k -j80
> 
> You need to be careful that the assembler and linker actually used match
> gcc's idea thereof: 
> 
> 	https://gcc.gnu.org/install/specific.html#x-x-solaris2
> 
> Best specify all of --build sparcv9-sun-solaris2.11 (if you're
> bootstrapping with a 64-bit-default gcc/g++) and
> 
> 	--with-as=/usr/gnu/bin/as (or /opt/cfarm/binutils-latest-64/bin/as)
> 	--with-gnu-as
> 
> (/usr/bin/as works too, but you need to specify both the path and
> --without-gnu-as)
> 
> 	--with-ld=/usr/bin/ld
> 	--without-gnu-ld
> 
> Having two different assemblers and linkers (Solaris and GNU) available
> can lead to confusion if you rely on PATH alone.

Ok, what's the minimum configuration I need to build here?

srcdir/configure --build=sparc-sun-solaris2.11

srcdir/configure --build=sparc-sun-solaris2.11 --without-gnu-as
--without-gnu-ld

??

I really don't care how it builds, I just want the bare minimum so I can
bootstrap and run tests.

A minor rant, but why can't all this be set up automatically in the compile
farm machines?  Keeping track of minor nuances of each architecture is
distracting.  They should all be set up, whether by setting default paths in
/etc/profile or whatever, or by having the relevant patches in GCC's source
base, such that they work with src/configure && make.

I know this isn't your fault, but if more cfarm boxes where set up to go with
no surprises, I'd add more boxen to my testing harness.

> 
> > gmake[3]: Leaving directory '/home/aldyh/bld/clean'
> > Comparing stages 2 and 3
> > Bootstrap comparison failure!
> > gcc/tree-vect-stmts.o differs
> 
> I'm not seeing this myself.

Dunno.  It could be the particular revision was broken??

  parent reply	other threads:[~2024-05-16 12:50 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-08 12:59 [Bug bootstrap/114985] New: " seurer at gcc dot gnu.org
2024-05-08 15:00 ` [Bug bootstrap/114985] " seurer at gcc dot gnu.org
2024-05-08 15:35 ` aldyh at gcc dot gnu.org
2024-05-08 16:34 ` seurer at gcc dot gnu.org
2024-05-08 16:34 ` aldyh at gcc dot gnu.org
2024-05-08 17:06 ` [Bug ipa/114985] " pinskia at gcc dot gnu.org
2024-05-08 20:33 ` aldyh at gcc dot gnu.org
2024-05-08 22:28 ` seurer at gcc dot gnu.org
2024-05-09 14:21 ` seurer at gcc dot gnu.org
2024-05-09 16:27 ` dje at gcc dot gnu.org
2024-05-09 21:54 ` aldyh at gcc dot gnu.org
2024-05-09 22:36 ` aldyh at gcc dot gnu.org
2024-05-10  9:27 ` aldyh at gcc dot gnu.org
2024-05-10 12:13 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-05-10 12:49 ` hubicka at gcc dot gnu.org
2024-05-10 14:38 ` segher at gcc dot gnu.org
2024-05-10 16:15 ` jamborm at gcc dot gnu.org
2024-05-11  9:47 ` aldyh at gcc dot gnu.org
2024-05-11  9:48 ` aldyh at gcc dot gnu.org
2024-05-13 14:06 ` jamborm at gcc dot gnu.org
2024-05-15 20:49 ` jamborm at gcc dot gnu.org
2024-05-15 21:06 ` amacleod at redhat dot com
2024-05-16  8:16 ` aldyh at gcc dot gnu.org
2024-05-16  9:59 ` cvs-commit at gcc dot gnu.org
2024-05-16  9:59 ` cvs-commit at gcc dot gnu.org
2024-05-16 10:07 ` aldyh at gcc dot gnu.org
2024-05-16 10:58 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-05-16 11:49 ` aldyh at gcc dot gnu.org
2024-05-16 11:58 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-05-16 12:50 ` aldyh at gcc dot gnu.org [this message]
2024-05-16 12:56 ` aldyh at gcc dot gnu.org
2024-05-16 13:04 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-05-16 14:24 ` aldyh at gcc dot gnu.org
2024-05-16 19:06 ` segher 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-114985-4-GWa3ilS8nR@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).