This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug middle-end/47895] usage of __attribute__ ((__target__ ("xyz"))) with buitins
- From: "vincenzo.innocente at cern dot ch" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sat, 26 Feb 2011 09:55:04 +0000
- Subject: [Bug middle-end/47895] usage of __attribute__ ((__target__ ("xyz"))) with buitins
- Auto-submitted: auto-generated
- References: <bug-47895-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47895
--- Comment #2 from vincenzo Innocente <vincenzo.innocente at cern dot ch> 2011-02-26 09:55:03 UTC ---
I find that the solution with multiple files shifts the problem to the build
system, which is not necessarily an easier solution in all projects, and make
maintenance more difficult as more files need to be tracked for each single
algorithm.
I would much prefer a solution that is fully confined to the source code
without involving the configuration and build system.
In any case at the moment there is a clear unbalance between plane c code, for
which a single compilation unit with multiple functions for different "targets"
do work, and code exploiting builtins for which __attribute__ ((__target__
("xyz"))) is not ineffective.
I consider this behavior a defect.