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 49A13385DC35; Mon, 18 May 2020 09:32:31 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 49A13385DC35
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1589794351;
 bh=riaXoGJQHjmLC6aqJwjSsfu4PPuWkM838Ag93w3JlBM=;
 h=From:To:Subject:Date:In-Reply-To:References:From;
 b=IDzvJASwP6dJ6YoheycimmAxCFRtUUZMNVjYT7H0foBTl7VoohjcBIsm1iwoZVkof
 Zg97uoqN15qPinLZKGkJNgBXnJ20gQWOXjw07XxR2QJ8wEwKbFVm/6oOtQf2EukPb+
 9tPTOKj+E0LmmyNJgIcqS9ANE94g8T2yXfnjXLZU=
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/94934] Failure to inline addv
Date: Mon, 18 May 2020 09:32:31 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 11.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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-94934-4-9C4ZuKIxVr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-94934-4@http.gcc.gnu.org/bugzilla/>
References: <bug-94934-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
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <http://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <http://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Mon, 18 May 2020 09:32:31 -0000

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

--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Gabriel Ravier from comment #3)
> In that case, it looks really easy to reimplemnet `-ftrapv` as literally
> just enabling `-fsanitize=3Dsigned-integer-overflow
> -fsanitize-undefined-trap-on-error`.

It shouldn't be literally that, because -ftrapv should be able to coexist w=
ith
other UBSan sanitizers (just not signed-integer-overflow) and e.g. let the
other UBSan sanitizers have different decision on what to do on error (the
trap. vs. fatal error vs. just diagnostics and continue).
And for -ftrapv we should consider using the library functions rather than
emitting code inline if it would be too large to match past behavior.=