From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id A3748385E012; Wed, 25 Mar 2020 09:28:59 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A3748385E012 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1585128539; bh=C6OHDo74aB9l4WlfW64TU2JKKsp5q+tqmIfhfZ3XKS4=; h=From:To:Subject:Date:In-Reply-To:References:From; b=JkKH0g/AAuj3AIDkyhnljcszh5CYriDOYR1+iOx1HKfsXCvpziKHuhi6M4er4wJ7E p4r+7mIJ7CI7iRrloaKg+CAzuEWftvrle8LWeOvqG2790r9BinqI/DlMAuhVWN9K9F g9Gtk3z9FE05WbF8BjuWyaBLjGO1OV5ZL15G7lbo= From: "marxin at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/94307] Provide a way to declare the *SAN exception handler -fsanitize-undefined-trap-on-error Date: Wed, 25 Mar 2020 09:28:59 +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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: marxin at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org X-Bugzilla-Target-Milestone: 11.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Mar 2020 09:28:59 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D94307 --- Comment #3 from Martin Li=C5=A1ka --- (In reply to Richard Biener from comment #1) > But isn't the default without -fsanitize-undefined-trap-on-error already > calling > a library routine that the kernel could override? They don't want to implement all the: call __ubsan_handle_add_overflow call __ubsan_handle_divrem_overflow call __ubsan_handle_dynamic_type_cache_miss call __ubsan_handle_invalid_builtin call __ubsan_handle_load_invalid_value call __ubsan_handle_mul_overflow call __ubsan_handle_negate_overflow call __ubsan_handle_nonnull_arg call __ubsan_handle_out_of_bounds call __ubsan_handle_pointer_overflow call __ubsan_handle_shift_out_of_bounds call __ubsan_handle_sub_overflow call __ubsan_handle_type_mismatch_v1 ... run-time entry points.=