public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/102772] [12 regression] g++.dg/torture/pr80334.C FAILs Date: Mon, 21 Mar 2022 12:01:53 +0000 [thread overview] Message-ID: <bug-102772-4-p2GfBpvi2Z@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102772-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102772 --- Comment #11 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> --- > --- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> --- > Is this with Solaris as or GNU as? both. > I've tried to reproduce it with a cross from x86_64-linux to > i386-pc-solaris2.11 and have > #define HAVE_AS_TLS 1 > in auto-host.h, but I don't see any movaps instructions in pointer2.f90 with > -O2 -fopenmp or -O3 -fopenmp. I do, both at -O2 and -O3: pointer2.s: movaps %xmm1, thr.1@ntpoff(%ebx) pointer2.s: movaps %xmm2, thr.1@ntpoff+16(%ebx) > When I add -msse2 to command line, I see some but it is unclear which exact is > it. > So, can you please attach pointer2.s and say on which exact insn it fails? Will do. Thread 49 received signal SIGSEGV, Segmentation fault. [Switching to Thread 2 (LWP 2)] 0x0805181a in MAIN__._omp_fn.0 () 1: x/i $pc => 0x805181a <MAIN__._omp_fn.0+42>: movaps %xmm1,-0x28(%ebx) (gdb) x/10i $pc-10 0x8051810 <MAIN__._omp_fn.0+32>: shlb $0x46,-0x75(%ebx,%eiz,1) 0x8051815 <MAIN__._omp_fn.0+37>: adc %dh,%bl 0x8051817 <MAIN__._omp_fn.0+39>: movq (%eax),%mm1 => 0x805181a <MAIN__._omp_fn.0+42>: movaps %xmm1,-0x28(%ebx) 0x8051821 <MAIN__._omp_fn.0+49>: movdqu 0x10(%eax),%xmm2 0x8051826 <MAIN__._omp_fn.0+54>: movaps %xmm2,-0x18(%ebx) (gdb) p/x $ebx $1 = 0xfe1202c0 > And also attach your auto-host.h? Sure: I'm attaching the gas one. The only obviously tls-related differences between the two are --- master/11.4-gcc/build/gcc/auto-host.h 2022-03-20 21:20:00.738284645 +0 000 +++ master/11.4-gcc-gas/build/gcc/auto-host.h 2022-03-21 03:06:50.783523035 +0 000 [...] @@ -538 +538 @@ -#define HAVE_AS_IX86_TLSGDPLT 1 +/* #undef HAVE_AS_IX86_TLSGDPLT */ @@ -550 +550 @@ -#define HAVE_AS_IX86_TLSLDMPLT 1 +#define HAVE_AS_IX86_TLSLDMPLT 0
next prev parent reply other threads:[~2022-03-21 12:01 UTC|newest] Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-15 11:39 [Bug target/102772] New: " ro at gcc dot gnu.org 2021-10-15 11:40 ` [Bug target/102772] " ro at gcc dot gnu.org 2021-10-15 11:40 ` ro at gcc dot gnu.org 2021-10-15 11:40 ` ro at gcc dot gnu.org 2021-10-15 12:06 ` hjl.tools at gmail dot com 2021-10-15 13:02 ` rguenth at gcc dot gnu.org 2021-10-15 14:29 ` ro at CeBiTec dot Uni-Bielefeld.DE 2021-10-15 20:44 ` hjl.tools at gmail dot com 2021-11-16 11:51 ` jakub at gcc dot gnu.org 2021-11-23 12:36 ` ro at gcc dot gnu.org 2022-03-17 15:05 ` jakub at gcc dot gnu.org 2022-03-17 15:14 ` ro at CeBiTec dot Uni-Bielefeld.DE 2022-03-21 11:44 ` jakub at gcc dot gnu.org 2022-03-21 12:01 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message] 2022-03-21 12:03 ` ro at gcc dot gnu.org 2022-03-21 12:03 ` ro at gcc dot gnu.org 2022-03-21 13:17 ` jakub at gcc dot gnu.org 2022-03-21 13:31 ` jakub at gcc dot gnu.org 2022-03-22 15:12 ` ro at CeBiTec dot Uni-Bielefeld.DE 2022-03-22 17:00 ` jakub at gcc dot gnu.org 2022-03-23 13:56 ` ro at CeBiTec dot Uni-Bielefeld.DE 2022-03-23 14:11 ` jakub at gcc dot gnu.org 2022-03-23 14:17 ` jakub at gcc dot gnu.org 2022-03-25 12:48 ` ro at CeBiTec dot Uni-Bielefeld.DE 2022-03-25 12:53 ` ro at CeBiTec dot Uni-Bielefeld.DE 2022-03-25 12:54 ` jakub at gcc dot gnu.org 2022-03-25 13:00 ` ro at CeBiTec dot Uni-Bielefeld.DE 2022-03-25 13:06 ` jakub at gcc dot gnu.org 2022-03-25 13:13 ` ro at CeBiTec dot Uni-Bielefeld.DE 2022-03-25 13:18 ` jakub at gcc dot gnu.org 2022-03-25 13:22 ` ro at gcc dot gnu.org 2022-03-25 13:49 ` jakub at gcc dot gnu.org 2022-03-30 14:06 ` cvs-commit at gcc dot gnu.org 2022-03-30 14:45 ` jakub at gcc dot gnu.org 2022-03-30 14:52 ` redi at gcc dot gnu.org 2022-03-30 14:56 ` redi at gcc dot gnu.org 2022-03-30 15:04 ` redi at gcc dot gnu.org 2022-03-30 15:13 ` redi at gcc dot gnu.org 2022-03-30 15:23 ` jakub at gcc dot gnu.org 2022-03-31 13:46 ` ro at CeBiTec dot Uni-Bielefeld.DE 2022-03-31 13:47 ` ro at gcc dot gnu.org 2022-03-31 14:16 ` redi at gcc dot gnu.org 2022-03-31 14:18 ` redi at gcc dot gnu.org 2022-03-31 14:49 ` jakub at gcc dot gnu.org 2022-03-31 15:15 ` redi at gcc dot gnu.org 2022-03-31 15:47 ` jakub at gcc dot gnu.org 2022-04-04 11:54 ` jakub at gcc dot gnu.org 2022-04-11 9:13 ` jakub at gcc dot gnu.org 2022-04-11 14:19 ` ro at CeBiTec dot Uni-Bielefeld.DE 2022-04-11 14:19 ` ro at CeBiTec dot Uni-Bielefeld.DE 2022-04-11 15:29 ` jakub at gcc dot gnu.org 2022-04-12 7:53 ` jakub at gcc dot gnu.org 2022-04-13 14:47 ` ro at CeBiTec dot Uni-Bielefeld.DE 2022-05-06 8:31 ` [Bug target/102772] [12/13 " jakub at gcc dot gnu.org 2023-05-08 12:22 ` [Bug target/102772] [12/13/14 " rguenth at gcc dot gnu.org
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=bug-102772-4-p2GfBpvi2Z@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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).