Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Guinevere Larsen <guinevere@redhat.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/testsuite: skip gdb.threads/omp-par-scope.exp with clang
Date: Wed, 27 Nov 2024 15:50:27 -0300	[thread overview]
Message-ID: <e92d512c-3ff9-424b-a4bf-ef79b3156b7d@redhat.com> (raw)
In-Reply-To: <20241127111402.048359b9@f40-zbm-amd>

On 11/27/24 3:14 PM, Kevin Buettner wrote:
> On Mon, 25 Nov 2024 15:42:25 -0300
> Guinevere Larsen <guinevere@redhat.com> wrote:
>
>> Since 2020 it has been reported to clang[1] that the debug information
>> around OpenMP is insufficient.  The OpenMP section is not declared
>> within the correct scope, and instead clang marks as if the section was
>> a function in the global scope.  This causes several failures in the
>> test gdb.threads/omp-par-scope.exp when using clang to test GDB.
>>
>> Since this isn't a true failure of GDB, and there is little expectation
>> that clang will be able to fix this soon, this commit disables the
>> aforementioned test when clang is being used.
>>
>> [1] https://github.com/llvm/llvm-project/issues/44236
> I thought at first that it might make sense to XFAIL the problematic
> tests.  But after running it for myself, I see that clang has so many
> problems that I now agree that it makes sense to disable the test
> entirely (for clang).
>
> One nit though...
>
>> +if { [test_compiler_info "clang*"] } {
>> +    # Clang doesn't add OpenMP information in the correct scope,
>> +    # so all relevant tests here will fail.  See here for more info:
>> +    # https://github.com/llvm/llvm-project/issues/44236
>> +    unsupported "Clang doesn't add required info for the test"
> Could you change the message to:
>
>    "Clang doesn't provided the required debuginfo for this test"
>
> ?
>
>> +    return
>> +}
>> +
> With that nit fixed...
>
> Approved-by: Kevin Buettner <kevinb@redhat.com>
>
pushed with the nit fixed! Thanks for the quick review

-- 
Cheers,
Guinevere Larsen
She/Her/Hers


      reply	other threads:[~2024-11-27 18:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-25 18:42 Guinevere Larsen
2024-11-27 18:14 ` Kevin Buettner
2024-11-27 18:50   ` Guinevere Larsen [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=e92d512c-3ff9-424b-a4bf-ef79b3156b7d@redhat.com \
    --to=guinevere@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=kevinb@redhat.com \
    /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