On 1/31/2015 02:55, Jonathan Wakely wrote:
> On 30 January 2015 at 21:39, DJ Delorie wrote:
>>
>> pins...@gmail.com writes:
>>> No because they are c++ code so capital C is correct.
>>
>> However, we should avoid relying on case-sensitive file systems
>> (Windows) and use .cc or .cxx for C++ files
John Marino writes:
> Even if this issue is normally hidden due to gcc's makefiles
There are no makefiles involved.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
* DJ Delorie:
> pins...@gmail.com writes:
>> No because they are c++ code so capital C is correct.
>
> However, we should avoid relying on case-sensitive file systems
> (Windows) and use .cc or .cxx for C++ files
Aren't current Windows file systems case-preserving? Then they
shouldn't have no p
31.01.2015 14:10, Florian Weimer writes:
> Aren't current Windows file systems case-preserving? Then they
> shouldn't have no problems with .C files.
They are, but with some limitations: you can't create two files with
names differing only by case. I didn't try API functions, but here is
how it
> Aren't current Windows file systems case-preserving? Then they
> shouldn't have no problems with .C files.
They are case preserving, but not case sensitive. A wildcard search
for *.c will match foo.C and bar.c, and foo.c can be opened as FOO.C.
> Am 31.01.2015 um 21:21 schrieb DJ Delorie :
>
>
>> Aren't current Windows file systems case-preserving? Then they
>> shouldn't have no problems with .C files.
>
> They are case preserving, but not case sensitive. A wildcard search
> for *.c will match foo.C and bar.c, and foo.c can be opene
Hi,
I have been fighting with a strange problem on ARM where gcc puts all
the .rodata from a number of files lumped into a single .rodata
section even when -fdata-sections is used.
I searched and found a bug report here:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54303
which exactly describes
