------- Additional Comments From konrad dot schwarz at siemens dot com 2010-01-12 09:52 ------- (In reply to comment #1) > You can easily add m4 processing to gas yourself by writing a tiny wrapper > script. I see no need to add yet another feature to gas.
Well, like I wrote: > This option is important for > keasy integration with `make' default rules: e.g., in GNU make, > adding `-Wa,-m' > to ASFLAGS would enable using just the default rule catalog to compile such > sources; otherwise, a separate rule needs to be created and a naming scheme > (such as a suffix) be reserved for these files. A further reason is interaction with gcc: If as(1) is invoked via GCC (GNU make's default rules assume this), then the wrapper script is no longer trivial. In particular, .S files should still be operated on by the C pre-processor first, then by as(1) (including m4), and .s files emitted by the compiler should have access to m4 macro expansion; e.g., for GCC inline assembler. The interface between the GCC driver and as(1) is configured via the GCC spec file and the spec file would need to be adapted on a per-site basis. This is decidedly more complex compared to an additional flag in ASFLAGS, owing to the daunting syntax of spec files and the problem of automating such a change to the spec file during an installation process. -- http://sourceware.org/bugzilla/show_bug.cgi?id=10777 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. _______________________________________________ bug-binutils mailing list bug-binutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-binutils
