Re: How to write pattern for addition with carry operation

2008-06-07 Thread Uros Bizjak
Hello! The 16bit target that i am porting to gcc4.1.2 doesn't have any instructions for 32bit operations. But for addition and subtraction there is addc subc instructions that consider carry bit also. Presently i have patterns for SImode addition and subtraction such that the template will have

Re: How to write pattern for addition with carry operation

2008-06-07 Thread Mohamed Shafi
2008/6/7 Uros Bizjak <[EMAIL PROTECTED]>: > Hello! > >> The 16bit target that i am porting to gcc4.1.2 doesn't have any >> instructions for 32bit operations. But for addition and subtraction >> there is >> addc >> subc >> instructions that consider carry bit also. Presently i have patterns >> for S

4.3.0 and 4.3.1 don't build startfiles (crtXXX.o files)

2008-06-07 Thread Denys Vlasenko
Seen that 4.3.1 has been released, I tried to build i486-linux-uclibc cross-compiler. It went fine except for the detail that none of crt.o files are found in installation directory after "make install" For comparison, gcc 4.2.1's directory has them: # find -name 'crt*.o' ./lib/gcc/i486-linu

Warnings while building gcc-4.3-20080605 on Solaris2.10

2008-06-07 Thread rkiesling
The build of gcc-4.3-20080605 snapshot on holly with Solaris2.10 generated the following warnings. ../../gcc-4.3-20080605/gcc/expr.c: In function 'expand_expr_real_1': ../../gcc-4.3-20080605/gcc/expr.c:8024: warning: unknown conversion type character 'K' in format ../../gcc-4.3-20080605/gcc/expr

Re: Warnings while building gcc-4.3-20080605 on Solaris2.10

2008-06-07 Thread Andrew Pinski
On Sat, Jun 7, 2008 at 2:43 AM, rkiesling <[EMAIL PROTECTED]> wrote: > The build on holly used the native SunOS build tools, so YMMV. If not > a duplication of effort, should I submit a patch to correct these > warnings? Are these warnings during building stage1? If so ignore them. The differen

Re: Warnings while building gcc-4.3-20080605 on Solaris2.10

2008-06-07 Thread rkiesling
Andrew Pinski: > On Sat, Jun 7, 2008 at 2:43 AM, rkiesling <[EMAIL PROTECTED]> wrote: > > The build on holly used the native SunOS build tools, so YMMV. If not > > a duplication of effort, should I submit a patch to correct these > > warnings? > > Are these warnings during building stage1? If so

Re: How to write pattern for addition with carry operation

2008-06-07 Thread Uros Bizjak
On Sat, Jun 7, 2008 at 11:18 AM, Mohamed Shafi <[EMAIL PROTECTED]> wrote: >>> The 16bit target that i am porting to gcc4.1.2 doesn't have any >>> instructions for 32bit operations. But for addition and subtraction >>> there is >>> addc >>> subc >>> instructions that consider carry bit also. Presen

PR 36111 also relevant for 4.3.1

2008-06-07 Thread Lasse Kliemann
glibc 2.7 fails to build with gcc 4.3.1 (error messages given below). Investigating the error, I stumbled upon PR 36111. Applying the patch from http://gcc.gnu.org/viewcvs/trunk/gcc/ChangeLog?view=markup&pathrev=135221 makes gcc 4.3.1 build glibc OK (and everything else that I tried). Maybe so

4.3.1 fixincludes observation.

2008-06-07 Thread IainS
Hello all, Supplement to : http://gcc.gnu.org/ml/gcc-testresults/2008-06/msg00543.html http://gcc.gnu.org/ml/gcc-testresults/2008-06/msg00542.html Since this is not (AFAICT) reported by test summary; Most of it seems to be (presumably harmless) differences in white space. However note at the en

Re: [whopr] plugin interface design

2008-06-07 Thread Chris Lattner
On Jun 5, 2008, at 10:38 AM, Ian Lance Taylor wrote: Sure. But here's the thing: the gcc LTO approach involves having a regular object with a regular symbol table, and the IR is embedded in the object. In other words, we do know the symbol version information: it's in the symbol table of the

Re: [whopr] Design/implementation alternatives for the driver and WPA

2008-06-07 Thread Chris Lattner
On Jun 5, 2008, at 6:18 PM, Ian Lance Taylor wrote: How does the linker tell LTO that a symbol may be inlined, but must also be externally visible? The linker just tells LTO which symbols must remain. The LTO engine is free to inline anything that would improve codegen, with the exception t

Re: PR 36111 also relevant for 4.3.1

2008-06-07 Thread Uros Bizjak
Hello! glibc 2.7 fails to build with gcc 4.3.1 (error messages given below). Investigating the error, I stumbled upon PR 36111. Applying the patch from http://gcc.gnu.org/viewcvs/trunk/gcc/ChangeLog?view=markup&pathrev=135221

Re: How to write pattern for addition with carry operation

2008-06-07 Thread Ian Lance Taylor
"Mohamed Shafi" <[EMAIL PROTECTED]> writes: >> You can look into config/i386.md, how i.e. adddi3 is expanded and split in >> case of !TARGET_64BIT. > > But is it scheduling safe? > I mean you can't have addc executed before add. If i am right there > will be no dependency between the two instructi

Re: 4.3.0 and 4.3.1 don't build startfiles (crtXXX.o files)

2008-06-07 Thread Daniel Jacobowitz
On Sat, Jun 07, 2008 at 11:26:05AM +0200, Denys Vlasenko wrote: > Seen that 4.3.1 has been released, I tried to build > i486-linux-uclibc cross-compiler. You probably forgot to build libgcc. Are you using 'make all' / 'make install' or something more specific? Also check the libgcc configure.hos