public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "louis.granboulan.developer at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/53929] New: Bug in the use of Intel asm syntax when a global is named "and" Date: Wed, 11 Jul 2012 15:39:00 -0000 [thread overview] Message-ID: <bug-53929-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53929 Bug #: 53929 Summary: Bug in the use of Intel asm syntax when a global is named "and" Classification: Unclassified Product: gcc Version: 4.6.3 Status: UNCONFIRMED Severity: minor Priority: P3 Component: c AssignedTo: unassigned@gcc.gnu.org ReportedBy: louis.granboulan.developer@gmail.com The bug is quite simple: when using -masm=intel and a global named "and", as does not accept the output of the compiler. gcc (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3 preprocessed file is --- cut begin --- # 1 "a.c" # 1 "<interne>" # 1 "<command-line>" # 1 "a.c" int and = 0; int main() { return and; } --- cut end --- compiler output is --- cut begin --- gcc -v -masm=intel -save-temps a.c Utilisation des specs internes. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/i686-linux-gnu/4.6/lto-wrapper Target: i686-linux-gnu Configuré avec: ../src/configure -v --with-pkgversion='Ubuntu/Linaro 4.6.3-1ubuntu5' --with-bugurl=file:///usr/share/doc/gcc-4.6/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.6 --enable-shared --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.6 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --enable-plugin --enable-objc-gc --enable-targets=all --disable-werror --with-arch-32=i686 --with-tune=generic --enable-checking=release --build=i686-linux-gnu --host=i686-linux-gnu --target=i686-linux-gnu Modèle de thread: posix gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) COLLECT_GCC_OPTIONS='-v' '-masm=intel' '-save-temps' '-mtune=generic' '-march=i686' /usr/lib/gcc/i686-linux-gnu/4.6/cc1 -E -quiet -v -imultilib . -imultiarch i386-linux-gnu a.c -masm=intel -mtune=generic -march=i686 -fpch-preprocess -fstack-protector -o a.i le répertoire « /usr/local/include/i386-linux-gnu » est ignoré car inexistant le répertoire « /usr/lib/gcc/i686-linux-gnu/4.6/../../../../i686-linux-gnu/include » est ignoré car inexistant la recherche pour #include "..." débute ici : la recherche pour #include <...> débute ici: /usr/lib/gcc/i686-linux-gnu/4.6/include /usr/local/include /usr/lib/gcc/i686-linux-gnu/4.6/include-fixed /usr/include/i386-linux-gnu /usr/include Fin de la liste de recherche. COLLECT_GCC_OPTIONS='-v' '-masm=intel' '-save-temps' '-mtune=generic' '-march=i686' /usr/lib/gcc/i686-linux-gnu/4.6/cc1 -fpreprocessed a.i -quiet -dumpbase a.c -masm=intel -mtune=generic -march=i686 -auxbase a -version -fstack-protector -o a.s GNU C (Ubuntu/Linaro 4.6.3-1ubuntu5) version 4.6.3 (i686-linux-gnu) compiled by GNU C version 4.6.3, GMP version 5.0.2, MPFR version 3.1.0-p3, MPC version 0.9 heuristiques GGC: --param ggc-min-expand=100 --param ggc-min-heapsize=131072 GNU C (Ubuntu/Linaro 4.6.3-1ubuntu5) version 4.6.3 (i686-linux-gnu) compiled by GNU C version 4.6.3, GMP version 5.0.2, MPFR version 3.1.0-p3, MPC version 0.9 heuristiques GGC: --param ggc-min-expand=100 --param ggc-min-heapsize=131072 Compiler executable checksum: 09c248eab598b9e2acb117da4cdbd785 COLLECT_GCC_OPTIONS='-v' '-masm=intel' '-save-temps' '-mtune=generic' '-march=i686' as --32 -o a.o a.s a.s: Assembler messages: a.s:21: Error: invalid use of operator "and" --- cut end ---
next reply other threads:[~2012-07-11 15:39 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-07-11 15:39 louis.granboulan.developer at gmail dot com [this message] 2020-09-05 7:49 ` [Bug target/53929] " u1049321969 at caramail dot com 2020-09-06 18:42 ` asolokha at gmx dot com 2020-09-07 10:21 ` jakub at gcc dot gnu.org 2020-09-07 10:45 ` u1049321969 at caramail dot com 2020-09-07 10:54 ` jakub at gcc dot gnu.org 2020-10-26 10:17 ` jbeulich at suse dot com 2020-10-26 10:23 ` jbeulich at suse dot com 2020-12-31 15:06 ` [Bug target/53929] [meta-bug] -masm=intel with global symbol hjl.tools at gmail dot com 2020-12-31 15:07 ` hjl.tools at gmail dot com 2020-12-31 15:08 ` hjl.tools at gmail dot com 2020-12-31 15:08 ` hjl.tools at gmail dot com 2021-06-10 7:25 ` jbeulich at suse dot com 2023-05-04 4:20 ` pinskia at gcc dot gnu.org 2023-05-04 4:37 ` lh_mouse at 126 dot com 2023-05-04 6:21 ` jbeulich at suse dot com 2023-05-04 7:02 ` lh_mouse at 126 dot com 2023-05-04 7:15 ` jbeulich at suse dot com 2023-05-04 7:24 ` lh_mouse at 126 dot com 2023-05-04 13:14 ` lh_mouse at 126 dot com 2023-05-11 10:58 ` lh_mouse at 126 dot com 2023-05-11 11:35 ` jbeulich at suse dot com 2023-05-11 12:19 ` lh_mouse at 126 dot com 2023-05-11 14:30 ` jbeulich at suse dot com 2023-05-11 14:48 ` lh_mouse at 126 dot com 2024-01-18 5:38 ` lh_mouse at 126 dot com 2024-01-23 1:11 ` lh_mouse at 126 dot com 2024-01-24 2:16 ` lh_mouse at 126 dot com 2024-01-31 20:07 ` egallager 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-53929-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).