This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: fix for x86-64 failure of testsuite/gcc.dg/titype-1.c
- From: "Jan Beulich" <JBeulich at novell dot com>
- To: "Paolo Carlini" <pcarlini at suse dot de>
- Cc: <gcc-patches at gcc dot gnu dot org>
- Date: Wed, 09 Jun 2004 17:53:58 +0200
- Subject: Re: fix for x86-64 failure of testsuite/gcc.dg/titype-1.c
Yes, I did. But with all these burocratic rules I'm getting close to
give up publishing fixes for bugs... I understand this for large scale
changes, but for one-liners like this it doesn't seem appropriate. After
all, keeping local stuff in sync with the cvs is not effortless, however
much you try to automate it, especially when the number of changes you
have on top of that is high. Or maybe I just don't know about the magics
to resolve colliding patches automatically... Sorry, Jan
>>> Paolo Carlini <pcarlini@suse.de> 09.06.04 17:40:13 >>>
Jan Beulich wrote:
>--- /usr/local/src/gcc-3.4.0/gcc/config/i386/i386.c 2004-02-25
>
>
Did you get my message pointing out that, as a rule, patches should be
diffed
against current CVS sources?
Thanks,
Paolo.