[Bug driver/27237] New: gcc driver should pass -mthumb option to arm assembler

2006-04-20 Thread mf dot danger at gmail dot com
to arm assembler Product: gcc Version: unknown Status: UNCONFIRMED Severity: minor Priority: P3 Component: driver AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: mf dot danger at gmail dot com GCC build triplet

[Bug driver/27237] gcc driver should pass -mthumb option to arm assembler

2006-04-21 Thread mf dot danger at gmail dot com
--- Comment #2 from mf dot danger at gmail dot com 2006-04-21 20:08 --- I guess I didn't make it clear that this is a bug against the gcc _driver_ not the compiler. I am using gcc _driver_ to invoke gas to assemble an assembler *source* file. 'gcc -mthumb -c foo.S' shou

[Bug driver/27237] gcc driver should pass -mthumb option to arm assembler

2006-04-21 Thread mf dot danger at gmail dot com
--- Comment #3 from mf dot danger at gmail dot com 2006-04-21 20:24 --- Created an attachment (id=11313) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11313&action=view) Example .S file -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27237

[Bug driver/27237] gcc driver should pass -mthumb option to arm assembler

2006-04-21 Thread mf dot danger at gmail dot com
--- Comment #4 from mf dot danger at gmail dot com 2006-04-21 20:30 --- Perhaps a precise example would make this clearer. I have a human-written thumb assembler file. (see attached) I attempt to assemble it using arm-elf-gcc -v -g -mthumb -c -o bdidown.o bdidown.S The following

[Bug target/27237] gcc driver should pass -mthumb option to arm assembler

2006-04-21 Thread mf dot danger at gmail dot com
--- Comment #6 from mf dot danger at gmail dot com 2006-04-21 20:36 --- That's fine, so long as you turn it into a documentation bug and fix the documentation, as it's an option that's documented as being passed to the assembler. -- mf dot danger at gmail

[Bug target/27237] gcc driver should pass -mthumb option to arm assembler

2006-04-21 Thread mf dot danger at gmail dot com
--- Comment #8 from mf dot danger at gmail dot com 2006-04-21 22:43 --- On the question of documentation: >From the GNU Info node for invoking gas: Usually you do not need to use this `-Wa' mechanism, since many compiler command-line options are automatically passe

[Bug target/27237] gcc driver should pass -mthumb option to arm assembler

2006-04-21 Thread mf dot danger at gmail dot com
--- Comment #10 from mf dot danger at gmail dot com 2006-04-21 23:52 --- Gas is part of binutils, but the driver is part of gcc, and it *is* a violation of the principle of least astonishment to have to pass the same option two different ways through the driver depending on what option

[Bug target/27237] gcc driver should pass -mthumb option to arm assembler

2006-04-21 Thread mf dot danger at gmail dot com
--- Comment #12 from mf dot danger at gmail dot com 2006-04-22 01:16 --- actually, gcc itself says so: printf (_("\ \nOptions starting with -g, -f, -m, -O, -W, or --param are automatically\n\ passed on to the various sub-processes invoked by %s. In order to pass\n\ other op

[Bug target/27237] gcc driver should pass -mthumb option to arm assembler

2006-04-21 Thread mf dot danger at gmail dot com
--- Comment #14 from mf dot danger at gmail dot com 2006-04-22 01:51 --- I doubt there is anyone anywhere who would be able to devine that "various" meant this subset of the processes and not that. Further, the sentence that describes the use of '-W' specifically

[Bug c/28912] Non-functional -funsigned-char: signed/unsigned mismatch is reported

2006-09-25 Thread mf dot danger at gmail dot com
--- Comment #6 from mf dot danger at gmail dot com 2006-09-25 18:47 --- After consulting the oracle (In the this case ANSI X3.159-1989,) and being unable to find any information to support the claim that char is always different type than unsigned char or signed char, I'd like to