Displaying 4 results from an estimated 4 matches for "to17237327".
Did you mean:
a17237327
2009 Mar 13
4
[LLVMdev] promotion of return value.
...s the theory behind the patches that are used to fix
your bug.
However, we had this discussion last year, and it was decided to make
things more transparent by adding the aforementioned attributes. Please
look at the thread:
http://www.nabble.com/Troubling-promotion-of-return-value-to-Integer-...
-to17237327.html#a17237327
Regards,
Ali
> -----Original Message-----
> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu]
On
> Behalf Of Rafael Espindola
> Sent: Friday, March 13, 2009 2:07 AM
> To: LLVM Developers Mailing List
> Subject: Re: [LLVMdev] promotion of...
2009 Mar 13
0
[LLVMdev] promotion of return value.
...e happens
after we have generated llvm? That is, an optimization is transforming
a function that would return an i8 into one that returns i16 or i32?
Do you have a testcase for the problem you are trying to solve?
> http://www.nabble.com/Troubling-promotion-of-return-value-to-Integer-...
> -to17237327.html#a17237327
I am sorry I missed the thread. I will take a look.
> Regards,
> Ali
Cheers,
--
Rafael Avila de Espindola
Google | Gordon House | Barrow Street | Dublin 4 | Ireland
Registered in Dublin, Ireland | Registration Number: 368047
2009 Mar 13
0
[LLVMdev] promotion of return value.
2009/3/12 <Alireza.Moshtaghi at microchip.com>:
> What I was planning to do is to provide a default behavior that is
> consistent with what currently llvm does (promote to 32 bit)
> And then there will be control in clang for targets to do things
> differently.
> But I also understand you concern about gcc frontend; because the same
> thing has to also take place there....
2009 Mar 12
3
[LLVMdev] promotion of return value.
What I was planning to do is to provide a default behavior that is
consistent with what currently llvm does (promote to 32 bit)
And then there will be control in clang for targets to do things
differently.
But I also understand you concern about gcc frontend; because the same
thing has to also take place there....
We had long discussions about this last year, and this is what has been
decided.