Oleg Endo wrote:
> Just spotted two more of those "{ ... }".
> I will commit the attached version of the patch, OK?
OK.
Regards,
kaz
On Sun, 2012-04-08 at 08:01 +0900, Kaz Kojima wrote:
> Oleg Endo wrote:
> > In my original patch
> > http://gcc.gnu.org/ml/gcc-patches/2012-03/msg01315.html
> > I forgot two cases, which are addressed by the attached patch.
> > Tested with 'make all-gcc'.
> > OK?
>
> OK.
>
Just spotted two mor
Oleg Endo wrote:
> In my original patch
> http://gcc.gnu.org/ml/gcc-patches/2012-03/msg01315.html
> I forgot two cases, which are addressed by the attached patch.
> Tested with 'make all-gcc'.
> OK?
OK.
Regards,
kaz
Hi,
In my original patch
http://gcc.gnu.org/ml/gcc-patches/2012-03/msg01315.html
I forgot two cases, which are addressed by the attached patch.
Tested with 'make all-gcc'.
OK?
Cheers,
Oleg
ChangeLog:
* config/sh/sh.md: Use braced string notation where applicable.
Index: gcc/config/sh/s
Oleg Endo wrote:
> The attached patch adapts SH machine description to the braced string
> notation. This eliminates the need to have escaped strings-in-strings
> and hopefully makes the whole thing a bit easier to read.
>
> Tested by 'make all-gcc' and cross-compiling newlib.
>
> OK?
OK.
Reg
On Mar 19, 2012, at 3:00 PM, Oleg Endo wrote:
> The attached patch adapts SH machine description to the braced string
> notation.
Nice. My only comment would be, I think that { should start indented. I know
quite a few ports start in column 0, but... I think they are all wrong.
(define_insn
