public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/112358] [14 Regression] glibc -Wstringop-overflow= build failure
Date: Fri, 03 Nov 2023 08:04:59 +0000	[thread overview]
Message-ID: <bug-112358-4-OpesDbN7O1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112358-4@http.gcc.gnu.org/bugzilla/>

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |14.0
             Status|UNCONFIRMED                 |NEW
     Ever confirmed|0                           |1
   Last reconfirmed|                            |2023-11-03

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
I've added

cc1: note: destination object is likely at address zero

which indicates that we performed some jump threading that exposes a literal
NULL pointer we diagnose this on.  I see

(gdb) p debug_gimple_stmt (exp)
# .MEM_230 = VDEF <.MEM_252>
__atomic_store_4 (8B, 0, 0);

on the path

...

<bb 13> [local count: 14148527]:
_35 = __atomic_wide_counter_load_relaxed (&_dlfo_loaded_mappings_version); //
dl-find_object.c:260:10
_36 = (int) _35;
active_idx_37 = _36 & 1;
current_seg_38 = _dlfo_loaded_mappings[active_idx_37];
_347 = active_idx_37 ^ 1;
pretmp_348 = _dlfo_loaded_mappings[_347];
if (current_seg_38 != 0B) // dl-find_object.c:137:21
  goto <bb 84>; [94.50%]
else
  goto <bb 72>; [5.50%]

<bb 84> [local count: 13370358]:
goto <bb 23>; [100.00%]

... some loop ...

<bb 24> [local count: 13370358]:
# count_247 = PHI <count_147(93), count_246(95)>
remaining_to_add_43 = count_247 + prephitmp_317; // dl-find_object.c:662:10
if (pretmp_348 != 0B) // dl-find_object.c:150:14
  goto <bb 96>; [89.00%]
else
  goto <bb 27>; [11.00%]

<bb 27> [local count: 1470739]:
if (remaining_to_add_43 != 0) // dl-find_object.c:668:8
  goto <bb 98>; [47.09%]
else
  goto <bb 35>; [52.91%]

<bb 35> [local count: 778169]:
__sync_synchronize ();
__atomic_store_4 (8B, 0, 0); // [dl-find_object.c:644:132
goto <bb 38>; [100.00%]

  reply	other threads:[~2023-11-03  8:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-02 23:25 [Bug tree-optimization/112358] New: " jsm28 at gcc dot gnu.org
2023-11-03  8:04 ` rguenth at gcc dot gnu.org [this message]
2024-03-07 21:03 ` [Bug tree-optimization/112358] " law at gcc dot gnu.org
2024-05-07  7:42 ` [Bug tree-optimization/112358] [14/15 " rguenth 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-112358-4-OpesDbN7O1@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).