public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112297] New: Failure of pr100936.c on x86_64-apple-darwin21
Date: Mon, 30 Oct 2023 14:32:37 +0000	[thread overview]
Message-ID: <bug-112297-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 112297
           Summary: Failure of pr100936.c on x86_64-apple-darwin21
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: fxcoudert at gcc dot gnu.org
  Target Milestone: ---

FAIL: gcc.target/i386/pr100936.c (test for excess errors)

The error is:

pr100936.s:8:2: error: 32-bit absolute addressing is not supported in 64-bit
mode
        lea _var, %rax
        ^


The testcase is compiled to:

        .build_version macos,  12, 0
        .text
        .p2align 4
        .globl _baz
_baz:
LFB2:
# 12 "/Users/fx/gcc-upstream/gcc/testsuite/gcc.target/i386/pr100936.c" 1
        lea _var, %rax
# 0 "" 2
# 22 "/Users/fx/gcc-upstream/gcc/testsuite/gcc.target/i386/pr100936.c" 1
        mov %gs:(%rax), %eax
# 0 "" 2
        ret
LFE2:
        .globl _var
        .zerofill __DATA,__common,_var,4,2
        .section
__TEXT,__eh_frame,coalesced,no_toc+strip_static_syms+live_support
EH_frame1:
        .set L$set$0,LECIE1-LSCIE1
        .long L$set$0
LSCIE1:
        .long   0
        .byte   0x3
        .ascii "zR\0"
        .uleb128 0x1
        .sleb128 -8
        .uleb128 0x10
        .uleb128 0x1
        .byte   0x10
        .byte   0xc
        .uleb128 0x7
        .uleb128 0x8
        .byte   0x90
        .uleb128 0x1
        .align 3
LECIE1:
LSFDE1:
        .set L$set$1,LEFDE1-LASFDE1
        .long L$set$1
LASFDE1:
        .long   LASFDE1-EH_frame1
        .quad   LFB2-.
        .set L$set$2,LFE2-LFB2
        .quad L$set$2
        .uleb128 0
        .align 3
LEFDE1:
        .ident  "GCC: (GNU) 14.0.0 20231029 (experimental) [master
c6929b08558]"
        .subsections_via_symbols

             reply	other threads:[~2023-10-30 14:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-30 14:32 fxcoudert at gcc dot gnu.org [this message]
2023-10-30 14:34 ` [Bug target/112297] " fxcoudert at gcc dot gnu.org
2023-10-30 18:55 ` pinskia at gcc dot gnu.org
2024-03-29 19:38 ` [Bug testsuite/112297] " iains at gcc dot gnu.org
2024-04-03 14:56 ` cvs-commit at gcc dot gnu.org
2024-04-21 13:01 ` cvs-commit 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-112297-4@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).