Re: build error in libgcc

Mike Stump writes: > A make clean followed by a make in the libgcc directory results in: > > ../../../../gcc/libgcc/config/i386/cpuinfo.c:23:25: fatal error: > auto-target.h: No such file or directory > #include "auto-target.h" > > Oh, the the old days, we'd just add a dependancy… If someone kn

Re: Compiling GCC under Cygwin

Hi Angelo, well, after a somewhat bumpy start on the Cygwin list, I did get the information I needed. It turned out that the directories and files I had created under Windows had the permission 000 according to Cygwin, but I could still read the files and enter the directories, because the Windows

Re: Compiling GCC under Cygwin

Il 21/06/2013 16.06, Arjen Markus ha scritto: Hi Angelo, well, after a somewhat bumpy start on the Cygwin list, I did get the information I needed. It turned out that the directories and files I had created under Windows had the permission 000 according to Cygwin, but I could still read the file

GCC internal re-architecture proposal

[ I foolishly sent this with the document as an attachment... hopefully it gets rejected and anyone interested can simply download the document from the wiki..] Over the past couple of months, I've slowly been putting together an action plan to help modernize GCC's source base. We've had vari

Re: GCC internal re-architecture proposal

On 06/21/2013 11:27 AM, Andrew MacLeod wrote: I hope this link will work :-)... http://gcc.gnu.org/wiki/AndrewMacLeod?action=AttachFile&do=view&target=gccrestructureplan2.1.odt Highlander or you can use this PDF file... http://gcc.gnu.org/wiki/AndrewMacLeod?action=AttachFile&do=view&target

Re: GCC internal re-architecture proposal

A few observations: * You don't mention anything about separating host-side and target-side configuration, which are also entangled. A slightly out-of-date list of target macros used in target-side code is at and a clean back-end class woul

Register allocator question

A question regarding regalloc (probably greg?) I understand that matching constraints can constrain allocation to re-use registers, e.g. for an 'add' actually has 2 instruction operands (instead of 3). This is documented well. But what about if I do not necessarily constrain the output template, e

Re: GCC internal re-architecture proposal

On 06/21/2013 12:16 PM, Joseph S. Myers wrote: A few observations: * You don't mention anything about separating host-side and target-side configuration, which are also entangled. A slightly out-of-date list of target macros used in target-side code is at

Re: GCC internal re-architecture proposal

> * Various cases of front-end folding are to get better warnings, e.g. to > detect that in a signed-to-unsigned conversion the converted value is in > fact never negative. I don't see this issue mentioned in the document. Tree front-end folding, or more precisely folding of expressions generated

Re: Register allocator question

On Fri, Jun 21, 2013 at 9:22 AM, Hendrik Greving wrote: > A question regarding regalloc (probably greg?) > > I understand that matching constraints can constrain allocation to > re-use registers, e.g. for an 'add' actually has 2 instruction > operands (instead of 3). This is documented well. But w

Re: build error in libgcc

On Thu, Jun 20, 2013 at 6:25 PM, Mike Stump wrote: > A make clean followed by a make in the libgcc directory results in: > > ../../../../gcc/libgcc/config/i386/cpuinfo.c:23:25: fatal error: > auto-target.h: No such file or directory > #include "auto-target.h" > > Oh, the the old days, we'd just

Re: build error in libgcc

2013/6/22 Ian Lance Taylor : > On Thu, Jun 20, 2013 at 6:25 PM, Mike Stump wrote: >> A make clean followed by a make in the libgcc directory results in: >> >> ../../../../gcc/libgcc/config/i386/cpuinfo.c:23:25: fatal error: >> auto-target.h: No such file or directory >> #include "auto-target.h"

Re: build error in libgcc

Chung-Ju Wu writes: > clean: > - -rm -f auto-target.h libgcc_tm.h libgcc.map > + -rm -f libgcc_tm.h libgcc.map > -rm -f libgcc_tm.stamp stamp-h stmp-ldirs Same for stamp-h. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 0