public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/107940] temp_directory_path testcase broken
Date: Wed, 30 Nov 2022 22:06:19 +0000	[thread overview]
Message-ID: <bug-107940-4-x3gWLvN9xc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107940-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #1)
> (In reply to laurent.alfonsi@linaro.org from comment #0)
> > This may be linked to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90787.
> > But, I confirm my toolchain is based on trunk (13.0), and contains the 90787
> > fix.
> 
> No, I don't think it's related to that in any way.
> 
> valgrind and asan are both clean when running that test on
> x86_64-pc-linux-gnu.
> 
> Where does valgrind say there are uninitialized values? Maybe the problem is
> in the unwinder.

I suspect the problem is the unwinder which is why I put PR 107678 and PR
107675 as see also bug reports. Both are those are aarch64 specific issues
relating to unwind issues against the trunk. This might be the same issue there
too.

  parent reply	other threads:[~2022-11-30 22:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-30 20:47 [Bug libstdc++/107940] New: " laurent.alfonsi at linaro dot org
2022-11-30 22:00 ` [Bug libstdc++/107940] " redi at gcc dot gnu.org
2022-11-30 22:06 ` pinskia at gcc dot gnu.org [this message]
2022-11-30 22:29 ` redi at gcc dot gnu.org
2022-11-30 22:49 ` laurent.alfonsi at linaro dot org
2022-12-01 14:23 ` redi at gcc dot gnu.org
2022-12-01 16:50 ` laurent.alfonsi at linaro dot org
2022-12-01 19:57 ` pinskia at gcc dot gnu.org
2022-12-03 21:24 ` laurent.alfonsi at linaro dot 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-107940-4-x3gWLvN9xc@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).