Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Tom Tromey <tom@tromey.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH] xfail gdb.base/break-on-linker-gcd-function.exp with Solaris ld [PR34534]
Date: Thu, 20 Aug 2026 20:02:42 +0200	[thread overview]
Message-ID: <yddv794hdq5.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <87jypku4oo.fsf@tromey.com> (Tom Tromey's message of "Thu, 20 Aug 2026 10:39:35 -0600")

Hi Tom,

>>>>>> "Rainer" == Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> writes:
>
> Rainer> Even though ld supports --gc-sections as an alias for the native -z
> Rainer> discard-unused=sections, this doesn't work in this particular case.
> Rainer> While the issue is under investigation, this patch xfail's the test when
> Rainer> Solaris ld is in use.
>
> Rainer> Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=34534
>
> Rainer> Ok for trunk?
>
> A few tiny nits, ok with these fixed.
> Approved-By: Tom Tromey <tom@tromey.com>
>
> Rainer> +    # PR 34534
>
> Write 'PR testsuite/34534'.  This is the usual format and works
> automatically with Emacs due to gdb/.dir-locals.el.

fine with me: I've seen both forms used and wasn't sure which one is
preferred these days.  The full form certainly conveys more information.

> Rainer> +    if [regexp "Solaris Link Editors" $output] {
>
> Nowadays I think we brace if expressions, so "if {[...]} "

Will do, although it's not necessary.

Thanks.
	Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University

      reply	other threads:[~2026-08-20 18:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-20 14:09 Rainer Orth
2026-08-20 16:39 ` Tom Tromey
2026-08-20 18:02   ` Rainer Orth [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=yddv794hdq5.fsf@CeBiTec.Uni-Bielefeld.DE \
    --to=ro@cebitec.uni-bielefeld.de \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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