public inbox for binutils-cvs@sourceware.org
help / color / mirror / Atom feed
From: H.J. Lu <hjl@sourceware.org>
To: bfd-cvs@sourceware.org
Subject: [binutils-gdb] ld: Compile 2 CTF tests with -O2
Date: Mon, 25 Jul 2022 17:00:07 +0000 (GMT)	[thread overview]
Message-ID: <20220725170007.16CC8383A305@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=e4146092c3f147b8c395febc771edd7de23f724d

commit e4146092c3f147b8c395febc771edd7de23f724d
Author: H.J. Lu <hjl.tools@gmail.com>
Date:   Fri Jul 22 11:35:00 2022 -0700

    ld: Compile 2 CTF tests with -O2
    
    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.
    
            PR ld/29378
            * testsuite/ld-ctf/data-func-conflicted-vars.d: Compile with -O2.
            * testsuite/ld-ctf/data-func-conflicted.d: Likewise.

Diff:
---
 ld/testsuite/ld-ctf/data-func-conflicted-vars.d | 1 +
 ld/testsuite/ld-ctf/data-func-conflicted.d      | 1 +
 2 files changed, 2 insertions(+)

diff --git a/ld/testsuite/ld-ctf/data-func-conflicted-vars.d b/ld/testsuite/ld-ctf/data-func-conflicted-vars.d
index b278dfe5d84..4e570c6a61a 100644
--- a/ld/testsuite/ld-ctf/data-func-conflicted-vars.d
+++ b/ld/testsuite/ld-ctf/data-func-conflicted-vars.d
@@ -1,4 +1,5 @@
 #as:
+#cc: -O2
 #source: data-func-1.c
 #source: data-func-2.c
 #objdump: --ctf
diff --git a/ld/testsuite/ld-ctf/data-func-conflicted.d b/ld/testsuite/ld-ctf/data-func-conflicted.d
index 7a1b2d72234..b0db511a987 100644
--- a/ld/testsuite/ld-ctf/data-func-conflicted.d
+++ b/ld/testsuite/ld-ctf/data-func-conflicted.d
@@ -1,4 +1,5 @@
 #as:
+#cc: -O2
 #source: data-func-1.c
 #source: data-func-2.c
 #objdump: --ctf


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

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220725170007.16CC8383A305@sourceware.org \
    --to=hjl@sourceware.org \
    --cc=bfd-cvs@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).