public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/113403] [14 Regression] __builtin_nested_func_ptr_created, __builtin_nested_func_ptr should be dynamically linked by default
Date: Thu, 01 Feb 2024 20:10:35 +0000	[thread overview]
Message-ID: <bug-113403-4-DBcFQi8dRt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113403-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #18 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:03519175e21f4c2940aeb446cd2b81fdf995cad5

commit r14-8711-g03519175e21f4c2940aeb446cd2b81fdf995cad5
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Thu Feb 1 21:05:58 2024 +0100

    libgcc: Fix up i386/t-heap-trampoline [PR113403]

    I'm seeing
    ../../../libgcc/shared-object.mk:14: warning: overriding recipe for target
'heap-trampoline.o'
    ../../../libgcc/shared-object.mk:14: warning: ignoring old recipe for
target 'heap-trampoline.o'
    ../../../libgcc/shared-object.mk:17: warning: overriding recipe for target
'heap-trampoline_s.o'
    ../../../libgcc/shared-object.mk:17: warning: ignoring old recipe for
target 'heap-trampoline_s.o'

    This patch fixes that.

    2024-02-01  Jakub Jelinek  <jakub@redhat.com>

            PR libgcc/113403
            * config/i386/t-heap-trampoline: Add to LIB2ADDEHSHARED
            i386/heap-trampoline.c rather than aarch64/heap-trampoline.c.

      parent reply	other threads:[~2024-02-01 20:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-15 16:42 [Bug libgcc/113403] New: " fw at gcc dot gnu.org
2024-01-15 17:07 ` [Bug libgcc/113403] " iains at gcc dot gnu.org
2024-01-15 17:11 ` fw at gcc dot gnu.org
2024-01-15 17:24 ` iains at gcc dot gnu.org
2024-01-15 17:46 ` jakub at gcc dot gnu.org
2024-01-15 20:13 ` iains at gcc dot gnu.org
2024-01-15 21:36 ` jason at gcc dot gnu.org
2024-01-16  8:04 ` [Bug libgcc/113403] [14 Regression] " rguenth at gcc dot gnu.org
2024-01-16  9:00 ` fw at gcc dot gnu.org
2024-01-16  9:06 ` jakub at gcc dot gnu.org
2024-01-16  9:15 ` iains at gcc dot gnu.org
2024-01-16  9:22 ` jakub at gcc dot gnu.org
2024-01-16 11:12 ` fw at gcc dot gnu.org
2024-01-16 11:21 ` iains at gcc dot gnu.org
2024-01-21 23:37 ` iains at gcc dot gnu.org
2024-01-30  9:33 ` cvs-commit at gcc dot gnu.org
2024-01-30  9:33 ` cvs-commit at gcc dot gnu.org
2024-01-30 19:03 ` jakub at gcc dot gnu.org
2024-02-01 20:10 ` cvs-commit at gcc dot gnu.org [this message]

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-113403-4-DBcFQi8dRt@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).