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 testsuite/112729] gcc.target/i386/apx-interrupt-1.c etc. FAIL
Date: Tue, 28 Nov 2023 12:06:36 +0000	[thread overview]
Message-ID: <bug-112729-4-gTYXMIZXTc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112729-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112729

--- Comment #4 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #2 from Hongyu Wang <wwwhhhyyy333 at gmail dot com> ---
> The cfi scan fails was caused by -fno-omit-frame-pointer which force push the
> frame pointer first and the cfi info become different. By default we have
> -fomit-frame-pointer on linux, but not other targets. I'd just add
> -fomit-frame-pointer to these tests.

That's one of the first differences between Linux and other x86 targets
that come to mind.  I'd have sworn that's what I tried before reporting
the bug.  Apparently not ;-(

  parent reply	other threads:[~2023-11-28 12:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-27 15:10 [Bug testsuite/112729] New: " ro at gcc dot gnu.org
2023-11-27 15:10 ` [Bug testsuite/112729] " ro at gcc dot gnu.org
2023-11-27 15:14 ` ro at gcc dot gnu.org
2023-11-28  2:47 ` wwwhhhyyy333 at gmail dot com
2023-11-28  3:33 ` wwwhhhyyy333 at gmail dot com
2023-11-28 12:06 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
2023-11-28 12:11 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-11-28 12:27 ` ro at gcc dot gnu.org
2023-11-28 13:34 ` wwwhhhyyy333 at gmail dot com
2023-11-29  0:52 ` cvs-commit at gcc dot gnu.org
2023-11-29 13:52 ` cvs-commit at gcc dot gnu.org
2023-11-29 13:57 ` ro 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-112729-4-gTYXMIZXTc@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: 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).