RE: tree-sra.c and BIT_FIELD_REF?

2012-06-12 Thread Jay K
> On Tue, Jun 12, 2012 at 03:57:44PM +, Jay K wrote: > > > > Our front end is wierd. > > The input is unusually low level, and so are the trees it produces. > > I do have a hankering to fix that (or maybe just to output more portable C...) > > But for now: > > It doesn't use co

Re: tree-sra.c and BIT_FIELD_REF?

2012-06-12 Thread Martin Jambor
Hi, On Tue, Jun 12, 2012 at 03:57:44PM +, Jay K wrote: > > Our front end is wierd. > The input is unusually low level, and so are the trees it produces. > I do have a hankering to fix that (or maybe just to output more portable C...) > But for now: > It doesn't use component_refs, and doesn't

tree-sra.c and BIT_FIELD_REF?

2012-06-12 Thread Jay K
Our front end is wierd. The input is unusually low level, and so are the trees it produces. I do have a hankering to fix that (or maybe just to output more portable C...) But for now: It doesn't use component_refs, and doesn't define types much, but uses either either (type*)(base + offset) or bit

Re: [RFD+PATCH] ISA bit treatment on the MIPS platform

2012-06-12 Thread Pedro Alves
On 06/11/2012 07:20 PM, Joel Brobecker wrote: > From the ChangeLog entry, it seems like Pedro was involved in the making > of that patch, so perhaps he could be a good reviewer? All involvement I recall was updating a couple lines to new interfaces in the context of a merge from upstream. All e

Re: Is it possible to make gcc detect whether printf prints floating point numbers?

2012-06-12 Thread Thierry Moreau
Joseph S. Myers wrote: On Tue, 12 Jun 2012, Bin.Cheng wrote: I noticed that GCC now can check format string of printf functions, so I am wondering if it is possible to take advantage of this utility, by making gcc detect whether printf prints floating point number and then generate assembly dir

Re: Endless "declared 'static' but never defined" warnings with stage 2 & 3 compilers

2012-06-12 Thread Vincent Rivière
On 11/06/2012 21:20, t-rexky wrote: #include #include int main() { printf("%lf\n", acos(0.5)); return 0; } First, note that acos(0.5) is a "double" expression so its format should be %f. However %lf is tolerated and this should not cause any trouble. Second, the acos() call will be inte

Re: Is it possible to make gcc detect whether printf prints floating point numbers?

2012-06-12 Thread Joseph S. Myers
On Tue, 12 Jun 2012, Bin.Cheng wrote: > >> I noticed that GCC now can check format string of printf functions, so > >> I am wondering if it is possible to take advantage of this utility, by > >> making gcc detect whether printf prints floating point number and then > >> generate assembly directive

Re: GCC Making a new PASS

2012-06-12 Thread Richard Guenther
On Tue, Jun 12, 2012 at 8:34 AM, Satya Prakash Prasad wrote: > Thanks to all my issue got resolved. > > I placed the code in 'if block' checking cfun is NULL or not and > removed gcc_assert. It worked fine for me. > > My idea is to print the lines of source code gcc is compiling. Further > to that

Re: GCC Making a new PASS

2012-06-12 Thread Satya Prakash Prasad
Regarding requirement - yes. I believe that it would be a powerful debugging tool to develop. It would be so powerful for analyzing code flow of flows for very large projects - that an ordinary developer can understand code in minutes. Say I have 100,000,00 Lines of code. Debugging using GDB or any

RE: GCC Making a new PASS

2012-06-12 Thread Mailaripillai, Kannan Jeganathan
Hi Prakash, > statement ; print("%s %d\n", __FILE__, __LINE__); > So that when program is running I know which file which line of my program > is getting executed. Just curious to know. Is there any real world application/product where this will help? Can you give more context to this requireme