This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Double backslashes in fixincl header (__FD_ZERO macro)


On Thursday 05 May 2005 10:26 pm, Frank Heckenbach wrote:
> > I do not know where you got your code, but what you have is not what
> > was released and not what is under CVS.  Your patch to fixincl.x
> > will correct the deviation from the released source. I just downloaded
> > the distro from ftp.gnu.org:
> > 
> > > $ md5sum *tar.bz2
> > > d2cbfe8fc3205c1d7969b26377405778  gcc-core-3.4.3.tar.bz2
> 
> Script started on Fri May  6 07:14:34 2005
> # md5sum gcc-core-3.4.3.tar.bz2
> d2cbfe8fc3205c1d7969b26377405778  gcc-core-3.4.3.tar.bz2
> # tar xjf gcc-core-3.4.3.tar.bz2 \*.x
> # head -134 gcc-3.4.3/gcc/fixinc/fixincl.x | tail -7
>   do { \\\\\n\
>     int __d0, __d1; \\\\\n\
> __asm__ __volatile__(\"cld ; rep ; stosl\" \\\\\n\
>         \t: \"=&c\" (__d0), \"=&D\" (__d1) \\\\\n\

Hi Frank,

That is, indeed, very bizarre.  I opened that file and the lines that
are supposed to be continued with backslashes ended with:  \\\n\
which is correct.  After you extract it, you have:  \\\\\n\
which is not correct.  I am at a loss as to what to suggest.
I cannot apply your patch because "patch" just complains that
the changes have already been applied and would I like to reverse
it.  You would end up with lines ending in \\\\\\\\\n\  ;).
Sorry.

Regards, Bruce


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]