From: Andreas Schwab <schwab@linux-m68k.org>
To: Jan Beulich <jbeulich@suse.com>
Cc: Binutils <binutils@sourceware.org>,
Jim Wilson <wilson@tuliptree.org>,
Joseph Myers <josmyers@redhat.com>
Subject: Re: [PATCH v3 9/9] gas: drop scrubber states 14 and 15
Date: Sun, 11 Aug 2024 10:14:00 +0200 [thread overview]
Message-ID: <87a5hjmq7r.fsf@linux-m68k.org> (raw)
In-Reply-To: <32cdb0b9-1ba8-44b7-8bc4-a8159bb863c1@suse.com> (Jan Beulich's message of "Wed, 31 Jul 2024 14:06:04 +0200")
This breaks gcc:
https://build.opensuse.org/package/live_build_log/devel:gcc:next/gcc15:cross-arm-none-gcc15-bootstrap/openSUSE_Tumbleweed/x86_64
/home/abuild/rpmbuild/BUILD/gcc-15.0.0+git2871/obj-x86_64-suse-linux/./gcc/xgcc -B/home/abuild/rpmbuild/BUILD/gcc-15.0.0+git2871/obj-x86_64-suse-linux/./gcc/ -B/usr/arm-none-eabi/bin/ -B/usr/arm-none-eabi/lib/ -isystem /usr/arm-none-eabi/include -isystem /usr/arm-none-eabi/sys-include --sysroot=/usr/arm-suse-linux-gnueabi/sys-root -g -O2 -O2 -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -isystem ./include -fno-inline -g -DIN_LIBGCC2 -fbuilding-libgcc -fno-stack-protector -Dinhibit_libc -fno-inline -I. -I. -I../.././gcc -I../../../libgcc -I../../../libgcc/. -I../../../libgcc/../gcc -I../../../libgcc/../include -o _interwork_call_via_rX_s.o -MT _interwork_call_via_rX_s.o -MD -MP -MF _interwork_call_via_rX_s.dep -DSHARED -DL_interwork_call_via_rX -xassembler-with-cpp -c ../../../libgcc/config/arm/lib1funcs.S
../../../libgcc/config/arm/lib1funcs.S: Assembler messages:
../../../libgcc/config/arm/lib1funcs.S:200: Error: too many positional arguments
../../../libgcc/config/arm/lib1funcs.S:1978: Info: macro invoked from here
../../../libgcc/config/arm/lib1funcs.S:2057: conditional infixes are deprecated in unified syntax
make[2]: *** [Makefile:498: _interwork_call_via_rX_s.o] Error 1
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2024-08-11 8:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 11:51 [PATCH v3 0/9] gas: scrubber adjustments Jan Beulich
2024-07-31 11:54 ` [PATCH v3 1/9] gas: have scrubber also respect quoted labels Jan Beulich
2024-07-31 11:55 ` [PATCH v3 2/9] gas: respect CR_EOL also for scrubbing Jan Beulich
2024-07-31 11:56 ` [PATCH v3 3/9] Arm: respect line separators for .symver scrubber special case Jan Beulich
2024-07-31 11:57 ` [PATCH v3 4/9] m32r: move scrubber override to target header Jan Beulich
2024-07-31 11:58 ` [PATCH v3 5/9] Arm: relax gas testsuite whitespace expectations Jan Beulich
2024-07-31 11:59 ` [PATCH v3 6/9] aarch64: " Jan Beulich
2024-07-31 12:00 ` [PATCH v3 7/9] MIPS: " Jan Beulich
2024-07-31 19:53 ` Maciej W. Rozycki
2024-08-01 6:46 ` Jan Beulich
2024-08-02 11:13 ` Maciej W. Rozycki
2024-07-31 12:04 ` [PATCH v3 8/9] gas: have scrubber retain more whitespace Jan Beulich
2024-08-11 16:26 ` Dimitar Dimitrov
2024-08-11 21:51 ` H.J. Lu
2024-08-11 22:17 ` H.J. Lu
2024-07-31 12:06 ` [PATCH v3 9/9] gas: drop scrubber states 14 and 15 Jan Beulich
2024-08-11 8:14 ` Andreas Schwab [this message]
2024-08-11 8:45 ` Andreas Schwab
2024-08-12 7:48 ` Jan Beulich
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=87a5hjmq7r.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=binutils@sourceware.org \
--cc=jbeulich@suse.com \
--cc=josmyers@redhat.com \
--cc=wilson@tuliptree.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).