public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/113182] [14 Regression] FAIL: g++.dg/cpp0x/udlit-namespace.C  -std=c++14 execution test
Date: Mon, 08 Jan 2024 14:29:19 +0000	[thread overview]
Message-ID: <bug-113182-4-7ar4ZSpFxG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113182-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to John David Anglin from comment #5)
> The problem is TREE_SYMBOL_REFERENCED is not set for libfuncs.  This fixes
> problem on hppa64-hpux:
> 
> bash-5.1$ git diff gcc/varasm.cc
> diff --git a/gcc/varasm.cc b/gcc/varasm.cc
> index 69f8f8ee018..0a1cc022023 100644
> --- a/gcc/varasm.cc
> +++ b/gcc/varasm.cc
> @@ -2527,9 +2527,7 @@ process_pending_assemble_externals (void)
>    for (rtx list = pending_libcall_symbols; list; list = XEXP (list, 1))
>      {
>        rtx symbol = XEXP (list, 0);
> -      tree id = get_identifier (XSTR (symbol, 0));
> -      if (TREE_SYMBOL_REFERENCED (id))
> -       targetm.asm_out.external_libcall (symbol);
> +      targetm.asm_out.external_libcall (symbol);
>      }
> 
>    pending_assemble_externals = 0;
> 
> If you don't care about libfuncs, you could move the TREE_SYMBOL_REFERENCED
> check into the bpf target.

Then the bug is that it isn't set when they are actually referenced.
The whole point of the patch was avoid referencing something that isn't really
referenced.  And it wasn't specific to one backend, many backends simply used
to emit say externs for both signed and unsigned division when expansion saw
range of operands would allow both signed and unsigned division and so expanded
both to pick the cheaper one.

  parent reply	other threads:[~2024-01-08 14:29 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-30 18:03 [Bug other/113182] New: " danglin at gcc dot gnu.org
2023-12-30 18:30 ` [Bug middle-end/113182] " pinskia at gcc dot gnu.org
2023-12-30 18:38 ` dave.anglin at bell dot net
2023-12-30 19:19 ` danglin at gcc dot gnu.org
2023-12-30 19:26 ` danglin at gcc dot gnu.org
2024-01-01 20:41 ` danglin at gcc dot gnu.org
2024-01-08 14:19 ` rguenth at gcc dot gnu.org
2024-01-08 14:29 ` jakub at gcc dot gnu.org [this message]
2024-01-08 15:56 ` dave.anglin at bell dot net
2024-01-09 18:00 ` jakub at gcc dot gnu.org
2024-01-09 19:56 ` dave.anglin at bell dot net
2024-01-09 20:03 ` dave.anglin at bell dot net
2024-01-10 13:57 ` dave.anglin at bell dot net
2024-01-10 17:49 ` danglin at gcc dot gnu.org
2024-01-11 16:55 ` danglin at gcc dot gnu.org
2024-01-11 17:37 ` jakub at gcc dot gnu.org
2024-01-11 17:47 ` jakub at gcc dot gnu.org
2024-01-11 18:03 ` dave.anglin at bell dot net
2024-01-11 18:25 ` jakub at gcc dot gnu.org
2024-01-11 18:56 ` dave.anglin at bell dot net
2024-01-11 19:05 ` jakub at gcc dot gnu.org
2024-01-11 19:21 ` dave.anglin at bell dot net
2024-01-12 12:59 ` cvs-commit at gcc dot gnu.org
2024-01-12 13:06 ` jakub at gcc dot gnu.org

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-113182-4-7ar4ZSpFxG@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).