From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 67CD0385C40F; Wed, 31 Aug 2022 04:19:19 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 67CD0385C40F
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1661919559;
	bh=hAfhzMqf4fiNuoMj+US2YAfFwbsEHjm/N69A2z1dTXo=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=TQB8qNbxkJ2Kf+niKEsO9v6x+FZjYjAyDKi5KX+nt9ZqbhMPB5F458yi0b32W0IrE
	 73yyJQPL0Y8vDaLQ/4l3gnL2Uuf7pdzBWw39Vc5a+Z0NCe3k0R9j1Npy5dXmHRa8x8
	 ZeB170S66q5taaVl8arG4Hd9y0q1kI9Lk4rLTkmA=
From: "broly at mac dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/105614] mips64:
 sanitizer_platform_limits_linux.cpp:75:38: error: static assertion failed
Date: Wed, 31 Aug 2022 04:19:18 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 11.3.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: broly at mac dot com
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-105614-4-R0uIEhCGu1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-105614-4@http.gcc.gnu.org/bugzilla/>
References: <bug-105614-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

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

--- Comment #17 from gagan sidhu (broly) <broly at mac dot com> ---
(In reply to Xi Ruoyao from comment #16)
> (In reply to gagan sidhu (broly) from comment #15)
>=20
> > and also: https://gcc.gnu.org/git/gitweb.cgi?p=3Dgcc.git;h=3D9f943b2446=
f2d0
>=20
> Please don't use this.  I've already said why this is not correct in
> previous replies.
>=20
> The correct fix is https://reviews.llvm.org/D129749, which is not reviewed
> by upstream yet.  As libsanitizer is technically not a part of GCC we can=
not
> apply a fix before it's accepted by upstream.

thank you for this.

after reading the replies and applying
https://github.com/gcc-mirror/gcc/commit/ee915c72da2caf92697dbedf0d9d9730ce=
9aca7a
i thought hans' fix would do the trick since it was building, but then it h=
ad a
problem on another ABI (i jumped the gun, my bad).

this led me to conclude the problem could be fixed with a size macro for the
64/N32 ABIs but i don't know the code very well.

i can confirm these two commits fix the problem:
https://gcc.gnu.org/git/gitweb.cgi?p=3Dgcc.git;h=3D9f943b2446f2d0
https://reviews.llvm.org/D129749


thanks.

an aside:
not sure how much libsanitiser is used, and i suspect you're correct that i
could have done without it.=20

not sure how all of these problems arose between 11.3 and 12.2. nice to see
things are back on track.=