ouch. I had forgotten about this, which is now PR 54102.
-benjamin
On 26 July 2012 20:36, Simone Pellegrini wrote:
> Hello,
> I was experimenting with trailer function return types together with
> decltype to define a function whose return type depends on the recursive
> invocation of the function itself.
This question is not appropriate for this mailing list, wh
On Thu, 2012-07-26 at 10:51 -0700, Ian Lance Taylor wrote:
> On Thu, Jul 26, 2012 at 8:57 AM, Jon Beniston
> wrote:
> >
> > I'd like to try to optimise double word left shifts of sign/zero extended
> > operands if a widening multiply instruction is available. For the following
> > code:
> >
> > l
Hello,
I was experimenting with trailer function return types together with
decltype to define a function whose return type depends on the recursive
invocation of the function itself.
The basic idea is to be able to define a meta-function which takes a
variable number of arguments and arrange
On Thu, Jul 26, 2012 at 8:57 AM, Jon Beniston wrote:
>
> I'd like to try to optimise double word left shifts of sign/zero extended
> operands if a widening multiply instruction is available. For the following
> code:
>
> long long f(long a, long b)
> {
> return (long long)a << b;
> }
>
> ARM, MI
Thanks!
http://gcc.gnu.org/ml/gcc/2012-06/msg00128.html also mentions that
http header munging as the preferred method.
http://gcc.gnu.org/ml/gcc/2012-04/msg00597.html shows why ff & ie are right.
Thanks again!
-Dhruv.
On Thu, Jul 26, 2012 at 10:19 AM, Jonathan Wakely wrote:
> On 26 July 2012
On 26 July 2012 17:54, Dhruv Matani wrote:
> Hello,
>
> This page: http://gcc.gnu.org/onlinedocs/libstdc++/faq.html (and other
> pages) don't include a utf-8 charset in the content-type http header,
See http://gcc.gnu.org/ml/gcc/2012-04/msg00597.html and
http://gcc.gnu.org/ml/gcc/2012-06/msg00125.
Hello,
This page: http://gcc.gnu.org/onlinedocs/libstdc++/faq.html (and other
pages) don't include a utf-8 charset in the content-type http header,
which is causing the page to be rendered incorrectly in firefox. Is it
possible to fix that? Even though the html header contains the utf-8
line, fire
Hi,
I'd like to try to optimise double word left shifts of sign/zero extended
operands if a widening multiply instruction is available. For the following
code:
long long f(long a, long b)
{
return (long long)a << b;
}
ARM, MIPS etc expand to a fairly long sequenc
On Thu, 26 Jul 2012, Paulo J. Matos wrote:
> My target has 16bit chars.
As I explained before, support for such targets is extremely limited and
bitrotten (this applies whether it is BITS_PER_UNIT, CHAR_TYPE_SIZE or
both that are not 8) and a large amount of work, and global GCC expertise
and
On Mon, Jul 23, 2012 at 12:23:59PM +0100, Bryce McKinlay wrote:
> libgcc_s and libgcj contain a hack which renames
> _Unwind_FindEnclosingFunction to
> _darwin10_Unwind_FindEnclosingFunction on darwin targets. It appears
> this was introduced to work around an issue in OS X 10.6 where the
> _Unwind
Hello Everyone,
I have a question regarding build6_stat. I saw that in 7/25 merge,
someone removed this function. Why was it removed? I am currently using it in
my Cilk Plus branch. What is a work around for this? Am I allowed to put this
function back in?
Thanks,
Balaji V. Iyer.
On 26/07/2012 14:04, Richard Guenther wrote:
On Thu, Jul 26, 2012 at 1:21 PM, David Brown wrote:
On 26/07/2012 11:12, Richard Guenther wrote:
On Wed, Jul 25, 2012 at 8:25 PM, David Brown
wrote:
On 25/07/12 17:30, Richard Guenther wrote:
On Wed, Jul 25, 2012 at 4:07 PM, Selvaraj, Senthil
On Thu, Jul 26, 2012 at 2:32 PM, Paulo J. Matos wrote:
> On 26/07/12 13:27, Richard Guenther wrote:
>>>
>>> Why would the fill value in a memset call be required to fit in a host
>>> char?
>>
>>
>> Obviously because of the implementation detail of its caller.
>>
>> Richard.
>>
>
> Richard, I am so
On 07/26/2012 01:32 PM, Paulo J. Matos wrote:
> On 26/07/12 13:27, Richard Guenther wrote:
>>> Why would the fill value in a memset call be required to fit in a host char?
>>
>> Obviously because of the implementation detail of its caller.
>
> Richard, I am sorry if I was not more clear. I underst
On 26/07/12 13:27, Richard Guenther wrote:
Why would the fill value in a memset call be required to fit in a host char?
Obviously because of the implementation detail of its caller.
Richard.
Richard, I am sorry if I was not more clear. I understand that this is
required because the caller
On Thu, Jul 26, 2012 at 2:11 PM, Paulo J. Matos wrote:
> Hi,
>
> My target has 16bit chars.
> What I am seeing is that in a memset call, the call is not inlined by GCC
> whenever fill value is bigger than host char.
>
> This seems to be due to the code (GCC 4.6.5) in target_char_cast
> (builtins.c
Hi,
My target has 16bit chars.
What I am seeing is that in a memset call, the call is not inlined by
GCC whenever fill value is bigger than host char.
This seems to be due to the code (GCC 4.6.5) in target_char_cast
(builtins.c), called from expand_builtin_memset_args:
static int
target_cha
On Thu, Jul 26, 2012 at 1:21 PM, David Brown wrote:
> On 26/07/2012 11:12, Richard Guenther wrote:
>>
>> On Wed, Jul 25, 2012 at 8:25 PM, David Brown
>> wrote:
>>>
>>> On 25/07/12 17:30, Richard Guenther wrote:
On Wed, Jul 25, 2012 at 4:07 PM, Selvaraj, Senthil_Kumar
wrote:
On 26/07/2012 11:12, Richard Guenther wrote:
On Wed, Jul 25, 2012 at 8:25 PM, David Brown wrote:
On 25/07/12 17:30, Richard Guenther wrote:
On Wed, Jul 25, 2012 at 4:07 PM, Selvaraj, Senthil_Kumar
wrote:
Declaring a function with __attribute__((optimize("O0")) turns off
inlining for the t
On Wed, Jul 25, 2012 at 8:25 PM, David Brown wrote:
> On 25/07/12 17:30, Richard Guenther wrote:
>>
>> On Wed, Jul 25, 2012 at 4:07 PM, Selvaraj, Senthil_Kumar
>> wrote:
>>>
>>> Declaring a function with __attribute__((optimize("O0")) turns off
>>> inlining for the translation unit (atleast) con
On 07/26/2012 09:03 AM, Jon Beniston wrote:
> Hi Eric,
>
>>> I guess my question is what would I need to change to make it work
>>> like the ARM port? I can't see how this is being controlled.
>>
>> Try TARGET_PROMOTE_PROTOTYPES.
>
> Thanks, actually it does turn out to be this, but I was confuse
Hi Eric,
> > I guess my question is what would I need to change to make it work
> > like the ARM port? I can't see how this is being controlled.
>
> Try TARGET_PROMOTE_PROTOTYPES.
Thanks, actually it does turn out to be this, but I was confused by the
documentation. If this returns true, I see s
23 matches
Mail list logo
