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 96C613858C60; Tue, 26 Mar 2024 16:20:39 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 96C613858C60
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1711470039;
	bh=naTQEbLfhsVQuiEv5WdkVRFrJYLiad7SZLXMVb7nkoI=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=A0ooRVvwojFzlD5sb+OK/wMCRTWYz8DiAmTy8oW1wOmo+JfUPdBeL8ybm3YUgNeqT
	 7M0rvFzYYrxu3ySz0C/bzdaFlXD+Ark65QCd3vO+VvsAUb5O9I2qURYWG50wGw9/dG
	 /fgY5UOi8fGqJdh3YGoG5rcW7YWK/aYq9ShOyKUY=
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/114431] bpf: GCC generates unverifiable code for systemd
 restrict_fs_bpf
Date: Tue, 26 Mar 2024 16:20:38 +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: 14.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit 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-114431-4-rJB3Yuws1n@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-114431-4@http.gcc.gnu.org/bugzilla/>
References: <bug-114431-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=3D114431

--- Comment #5 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Cupertino Miranda <cupermir@gcc.gnu.o=
rg>:

https://gcc.gnu.org/g:fa60ac549649655a3f55e69f83d2e97423d3eb5c

commit r14-9677-gfa60ac549649655a3f55e69f83d2e97423d3eb5c
Author: Cupertino Miranda <cupertino.miranda@oracle.com>
Date:   Tue Mar 26 11:59:47 2024 +0000

    btf: Emit labels in DATASEC bts_offset entries.

    GCC was defining bts_offset entry to always contain 0.
    When comparing with clang, the same entry is instead a label to the
    respective variable or function. The assembler emits relocations for
    those labels.

    gcc/ChangeLog:
            PR target/114431
            * btfout.cc (get_name_for_datasec_entry): Add function.
            (btf_asm_datasec_entry): Print label when possible.

    gcc/testsuite/ChangeLog:
            * gcc.dg/debug/btf/btf-datasec-1.c: Correct for new
            implementation.
            * gcc.dg/debug/btf/btf-datasec-2.c: Likewise
            * gcc.dg/debug/btf/btf-pr106773.c: Likewise=