public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug jit/110466] jit.dg FAILs on ppc64le
Date: Wed, 28 Jun 2023 22:28:53 +0000	[thread overview]
Message-ID: <bug-110466-4-CwjIRcSVrA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110466-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #5)
> (In reply to Andrew Pinski from comment #4)
> > (In reply to David Malcolm from comment #3)
> > > 
> > >   Reading symbols from
> > > /home/dmalcolm/build/gcc/testsuite/jit4/jit-debuginfo.o...Dwarf Error: wrong
> > > version in compilation unit header (is 5, should be 2, 3, or 4) [in module
> > > /home/dmalcolm/build/gcc/testsuite/jit4/jit-debuginfo.o]
> > > 
> > > though I'm not sure if that's the cause of the error.
> > 
> > Those look depedenent on the binutils version that is in use. I suspect if
> > there is a newer version of binutils installed, it would just work. Dwarf5
> > was added to binutils version 2.35.2 . Though maybe it is finding the wrong
> > readelf ...
> 
> Or rather it is gdb that is complaining and a newer gdb version is needed.

Yeah; I think the gdb version is too old.

Adding the following patch turns this into an "unsupported" (on this host, at
least):

diff --git a/gcc/testsuite/jit.dg/jit.exp b/gcc/testsuite/jit.dg/jit.exp
index 3568dbb..8bf7e51 100644
--- a/gcc/testsuite/jit.dg/jit.exp
+++ b/gcc/testsuite/jit.dg/jit.exp
@@ -440,6 +440,10 @@ proc jit-check-debug-info { obj_file cmds match } {
         send $cmd
     }
     expect {
+       -re "Dwarf Error: wrong version in compilation unit header" {
+           set testcase [testname-for-summary]
+           unsupported "$testcase: gdb does not support dwarf version"
+       }
         -re $match { pass OK }
         default { fail FAIL }
     }

I'll try the combination of these patches on my regular x86_64 workstation...

  parent reply	other threads:[~2023-06-28 22:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-28 19:28 [Bug jit/110466] New: " mpolacek at gcc dot gnu.org
2023-06-28 19:29 ` [Bug jit/110466] " mpolacek at gcc dot gnu.org
2023-06-28 21:02 ` dmalcolm at gcc dot gnu.org
2023-06-28 21:38 ` dmalcolm at gcc dot gnu.org
2023-06-28 21:42 ` pinskia at gcc dot gnu.org
2023-06-28 21:43 ` pinskia at gcc dot gnu.org
2023-06-28 22:28 ` dmalcolm at gcc dot gnu.org [this message]
2023-06-30 15:20 ` cvs-commit at gcc dot gnu.org
2023-06-30 15:20 ` cvs-commit at gcc dot gnu.org
2023-06-30 16:01 ` dmalcolm at gcc dot gnu.org
2024-05-09 17:11 ` cvs-commit at gcc dot gnu.org
2024-05-09 17:11 ` cvs-commit at gcc dot gnu.org
2024-05-10 18:58 ` dmalcolm 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-110466-4-CwjIRcSVrA@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).