public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ammarfaizi2 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/105032] New: Compiling inline ASM x86 causing GCC stuck in an endless loop with 100% CPU usage Date: Wed, 23 Mar 2022 03:46:52 +0000 [thread overview] Message-ID: <bug-105032-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105032 Bug ID: 105032 Summary: Compiling inline ASM x86 causing GCC stuck in an endless loop with 100% CPU usage Product: gcc Version: 11.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: ammarfaizi2 at gmail dot com Target Milestone: --- Full story: https://lore.kernel.org/lkml/9cfcb296-9dfe-aef1-4209-20a3a95c50ba@gnuweeb.org/ Compiling inline ASM x86 causing GCC stuck in an endless loop with 100% CPU usage. ----------------------------------------- ammarfaizi2@integral2:/tmp$ gcc --version gcc (Ubuntu 11.2.0-7ubuntu2) 11.2.0 Copyright (C) 2021 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. ammarfaizi2@integral2:/tmp$ gcc -m32 -o test test.c # stuck here... ^C ammarfaizi2@integral2:/tmp$ ----------------------------------------- Reproducer: ----------------------------------------- #include <sys/mman.h> #include <stddef.h> #include <syscall.h> #define my_syscall6(num, arg1, arg2, arg3, arg4, arg5, arg6) \ ({ \ long _ret; \ register long _num asm("eax") = (num); \ register long _arg1 asm("ebx") = (long)(arg1); \ register long _arg2 asm("ecx") = (long)(arg2); \ register long _arg3 asm("edx") = (long)(arg3); \ register long _arg4 asm("esi") = (long)(arg4); \ register long _arg5 asm("edi") = (long)(arg5); \ long _arg6 = (long)(arg6); /* Always be in memory */ \ \ asm volatile ( \ "pushl %[_arg6]\n\t" \ "pushl %%ebp\n\t" \ "movl 4(%%esp), %%ebp\n\t" \ "int $0x80\n\t" \ "popl %%ebp\n\t" \ "addl $4,%%esp\n\t" \ : "=a"(_ret) \ : "r"(_num), "r"(_arg1), "r"(_arg2), "r"(_arg3), \ "r"(_arg4),"r"(_arg5), [_arg6]"m"(_arg6) \ : "memory", "cc" \ ); \ _ret; \ }) static void *__sys_mmap(void *addr, size_t length, int prot, int flags, int fd, off_t offset) { offset >>= 12; return (void *)my_syscall6(__NR_mmap2, addr, length, prot, flags, fd, offset); } int main(void) { __sys_mmap(NULL, 0x1000, PROT_READ|PROT_WRITE, MAP_ANONYMOUS|MAP_PRIVATE, -1, 0); return 0; }
next reply other threads:[~2022-03-23 3:46 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-23 3:46 ammarfaizi2 at gmail dot com [this message] 2022-03-23 3:52 ` [Bug middle-end/105032] " pinskia at gcc dot gnu.org 2022-03-23 4:05 ` crazylht at gmail dot com 2022-03-23 9:24 ` jakub at gcc dot gnu.org 2022-03-23 9:28 ` jakub at gcc dot gnu.org 2022-03-23 13:22 ` ammarfaizi2 at gmail dot com 2022-03-23 13:27 ` ammarfaizi2 at gmail dot com 2022-03-23 13:50 ` jakub at gcc dot gnu.org 2022-03-23 19:24 ` hjl.tools at gmail dot com 2022-03-29 12:49 ` vmakarov at gcc dot gnu.org 2022-03-30 17:02 ` vmakarov at gcc dot gnu.org 2022-03-30 17:10 ` cvs-commit at gcc dot gnu.org 2022-03-30 17:12 ` vmakarov at gcc dot gnu.org 2022-04-01 14:21 ` cvs-commit at gcc dot gnu.org 2022-07-28 18:43 ` hjl.tools at gmail dot com 2022-08-02 6:18 ` andrey.vihrov at gmail dot com
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-105032-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).