From: Andreas Schwab <schwab@suse.de>
To: Alexey Lapshin via Binutils <binutils@sourceware.org>
Cc: Alexey Lapshin <alexey.lapshin@espressif.com>,
Ivan Grokhotkov <ivan@espressif.com>,
Alexey Gerenkov <alexey.gerenkov@espressif.com>,
Anton Maklakov <anton.maklakov@espressif.com>
Subject: Re: [PATCH] bfd: xtensa: fix __stop_SECTION literal drop,
Date: Wed, 24 May 2023 13:38:50 +0200 [thread overview]
Message-ID: <mvmjzwydkmt.fsf@suse.de> (raw)
In-Reply-To: <c0211bc9c57be6c79c6d878ce147f63b657f461d.camel@espressif.com> (Alexey Lapshin via Binutils's message of "Tue, 4 Oct 2022 16:22:05 +0000")
Installed as obvious.
diff --git a/ld/testsuite/ld- b/ld/testsuite/ld-
deleted file mode 100644
index 6cea49add33..00000000000
--- a/ld/testsuite/ld-
+++ /dev/null
@@ -1,6 +0,0 @@
-#as:
-#ld:
-#objdump: -h
-#...
-.*TEST_SECTION\.literal[ ]*00000008.*
-#...
--
2.40.1
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
prev parent reply other threads:[~2023-05-24 11:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 16:22 Alexey Lapshin
2022-10-05 11:15 ` Nick Clifton
2023-05-24 11:38 ` Andreas Schwab [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=mvmjzwydkmt.fsf@suse.de \
--to=schwab@suse.de \
--cc=alexey.gerenkov@espressif.com \
--cc=alexey.lapshin@espressif.com \
--cc=anton.maklakov@espressif.com \
--cc=binutils@sourceware.org \
--cc=ivan@espressif.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).