[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [avr-gcc-list] SIGNAL and INTERRUPT overhead
From: |
David Brown |
Subject: |
Re: [avr-gcc-list] SIGNAL and INTERRUPT overhead |
Date: |
Wed, 24 Aug 2005 10:25:35 +0200 |
----- Original Message -----
From: "Haase Bjoern (PT-BEU/EMT) *" <address@hidden>
>Benjamin Titzer wrote:
>>That's a big problem with the usual way of building code, with functions
>>or set of related functions in
>>different files. When the compiler groks the files, it does not have all
>>the information that would help
>>it build a much better optimized code.
>IIUC, it would be sufficient to compile them at the same time. I.e. use gcc
file1.c file2.c -o >app.elf ...
Does compiling multiple C files at once have other benifits? And do you
have to link them at the same time? I have always thought that a line such
as "gcc file1.c file2.c -o app.elf" is equivilent to seperately compiling
each C file, and then linking them as a seperate pass - hence the
traditional makefile to re-compile modules to object files as necessary.
Regards,
David