public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/113711] New: Warning: instruction length of 16 bytes exceeds the limit of 15 Date: Thu, 01 Feb 2024 23:40:02 +0000 [thread overview] Message-ID: <bug-113711-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113711 Bug ID: 113711 Summary: Warning: instruction length of 16 bytes exceeds the limit of 15 Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: hjl.tools at gmail dot com CC: hongyuw at gcc dot gnu.org Target Milestone: --- Target: x86-64 [hjl@gnu-cfl-3 apx-1]$ cat x.c int foo (int off, int *ptr) { return 2000 + ptr[off + 2000]; } [hjl@gnu-cfl-3 apx-1]$ make x.s /export/build/gnu/tools-build/gcc-gitlab-debug/build-x86_64-linux/gcc/xgcc -B/export/build/gnu/tools-build/gcc-gitlab-debug/build-x86_64-linux/gcc/ -mapxf -O3 -mx32 -S x.c [hjl@gnu-cfl-3 apx-1]$ cat x.s .file "x.c" .text .p2align 4 .globl foo .type foo, @function foo: .LFB0: .cfi_startproc addl $2000, 8000(%esi,%edi,4), %eax ret .cfi_endproc .LFE0: .size foo, .-foo .ident "GCC: (GNU) 14.0.1 20240201 (experimental)" .section .note.GNU-stack,"",@progbits [hjl@gnu-cfl-3 apx-1]$ gcc -c x.s x.s: Assembler messages: x.s:9: Warning: instruction length of 16 bytes exceeds the limit of 15 [hjl@gnu-cfl-3 apx-1]$
next reply other threads:[~2024-02-01 23:40 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-01 23:40 hjl.tools at gmail dot com [this message] 2024-02-01 23:45 ` [Bug target/113711] " hjl.tools at gmail dot com 2024-02-01 23:56 ` [Bug target/113711] Warning: instruction length of 16 bytes exceeds the limit of 15 due to -mapxf and APX instruction set rejecting more than 15 bytes pinskia at gcc dot gnu.org 2024-02-02 12:35 ` [Bug target/113711] APX instruction set and instructions longer than 15 bytes (assembly warning) hjl.tools at gmail dot com 2024-02-02 14:45 ` hjl.tools at gmail dot com 2024-02-02 18:50 ` hongyuw at gcc dot gnu.org 2024-02-02 19:31 ` hjl.tools at gmail dot com 2024-02-02 20:03 ` hongyuw at gcc dot gnu.org 2024-02-02 20:58 ` hjl.tools at gmail dot com 2024-02-02 21:01 ` hjl.tools at gmail dot com 2024-02-03 15:38 ` hjl.tools at gmail dot com 2024-02-08 11:53 ` cvs-commit at gcc dot gnu.org 2024-02-20 7:43 ` 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-113711-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: 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).