public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nick Alcock <nick.alcock@oracle.com>
To: binutils@sourceware.org
Subject: Re: [PATCH] ld: Compile 2 CTF tests with -O2
Date: Mon, 25 Jul 2022 17:16:28 +0100	[thread overview]
Message-ID: <87a68xkw0z.fsf@esperi.org.uk> (raw)
In-Reply-To: <20220722183854.1557724-1-hjl.tools@gmail.com> (H. J. Lu via Binutils's message of "Fri, 22 Jul 2022 11:38:54 -0700")

On 22 Jul 2022, H. J. Lu via Binutils stated:

> When GCC 12 is used to build binutils with -O0, the following 2 tests
> failed:
>
> FAIL: Conflicted data syms, partially indexed, stripped, with variables
> FAIL: Conflicted data syms, partially indexed, stripped
>
> Compile 2 tests with -O2 to avoid test failures.

Ack, that works fine. I honestly didn't think that anyone would have
tried a -O0 compilation. I'm a bit surprised it depends on optimization
levels, though -- maybe the result has *too many* types and the
comparisons fail as a result?

Still, -O2 is a valid fix and doesn't stop the test checking what it's
supposed to, so go for it.

  reply	other threads:[~2022-07-25 16:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-22 18:38 H.J. Lu
2022-07-25 16:16 ` Nick Alcock [this message]
2022-07-25 16:59   ` H.J. Lu

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=87a68xkw0z.fsf@esperi.org.uk \
    --to=nick.alcock@oracle.com \
    --cc=binutils@sourceware.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).