public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jtaylor.debian at googlemail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/54344] illegal instructions generated with multiple "arch" function attributes Date: Mon, 13 Jan 2014 09:44:00 -0000 [thread overview] Message-ID: <bug-54344-4-fjY4DTreWH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54344-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54344 Julian Taylor <jtaylor.debian at googlemail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jtaylor.debian at googlemail dot c | |om --- Comment #1 from Julian Taylor <jtaylor.debian at googlemail dot com> --- you can work around the issue by putting the attributes only in the declarations not the definitions and the declaration must be placed before all definitions. int printf_avx(const char *restrict format, ...) __attribute__ ((__target__ ("arch=corei7-avx", "tune=corei7-avx"))) ; int printf_noavx(const char *restrict format, ...) __attribute__ ((__target__ ("arch=atom", "tune=atom"))) ; int printf_avx(const char *restrict format, ...) { va_list ap; ...
next prev parent reply other threads:[~2014-01-13 9:44 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-08-21 12:21 [Bug target/54344] New: Issue with multiple "arch=" " einar.sjurso+gnu at gmail dot com 2014-01-13 9:44 ` jtaylor.debian at googlemail dot com [this message] 2021-08-28 18:57 ` [Bug target/54344] illegal instructions generated with multiple "arch" " pinskia 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-54344-4-fjY4DTreWH@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).