> -Original Message-
> From: Richard Sandiford [mailto:rdsandif...@googlemail.com]
> Sent: 24 January 2014 16:34
> To: Paulo Matos
> Cc: gcc@gcc.gnu.org
> Subject: Re: ICE in trunk due to MEM with address in vector mode
>
> Paulo Matos writes:
> >> If we do support vector addresses than I
All,
gcc.c-torture/execute/pr58419.c has a call to getpid, and this causes
a linker error on the AVR (embedded) target. Is the call intentional,
and if yes, how should this be fixed for targets that don't support an
OS?
Regards
Senthil
Hello,
On a vector processor we can do a bswapsi with two instructions, by first
rotating half-words (16 bits) by 8 and then rotating full words by 16.
However, this means expanding:
(set (match_operand:SI 0 "register_operand" "")
(bswap:SI (match_operand:SI 1 "register_operand" "")))
to:
On 2013.12.17 at 07:43 +0100, Jakub Jelinek wrote:
> On Tue, Dec 17, 2013 at 08:45:13AM +0400, Konstantin Serebryany wrote:
> > Indeed, the compile time is dominated by asan_interceptors.cc:
> > % touch ~/llvm/projects/compiler-rt/lib/asan/asan_interceptors.cc
> > % date; ninja libclang_rt.asan-x8
Paulo Matos writes:
> On a vector processor we can do a bswapsi with two instructions, by first
> rotating half-words (16 bits) by 8 and then rotating full words by 16.
> However, this means expanding:
> (set (match_operand:SI 0 "register_operand" "")
> (bswap:SI (match_operand:SI 1 "regist
> -Original Message-
> From: Richard Sandiford [mailto:rdsandif...@googlemail.com]
> Sent: 27 January 2014 16:06
> To: Paulo Matos
> Cc: gcc@gcc.gnu.org
> Subject: Re: Mode change for bswap pattern expansion
>
> Paulo Matos writes:
> > On a vector processor we can do a bswapsi with two
On 01/26/2014 05:17 PM, Richard Sandiford wrote:
Marc Glisse writes:
I got an error that implies that "auto" is not usable, which would
mean that C++11 is not enabled, but I also got a warning that implied
that gnu++11 is "enabled by default".
error: ‘xdir’ does not name a type
warning: no
On Mon, 27 Jan 2014, Florian Weimer wrote:
On 01/26/2014 05:17 PM, Richard Sandiford wrote:
Any objections to changing it to "this warning is enabled by default"
or "warning enabled by default"? Or is that too verbose?
The second one looks fine to me, need to find a real reviewer now ;-)
We
Paulo Matos writes:
>> -Original Message-
>> From: Richard Sandiford [mailto:rdsandif...@googlemail.com]
>> Sent: 27 January 2014 16:06
>> To: Paulo Matos
>> Cc: gcc@gcc.gnu.org
>> Subject: Re: Mode change for bswap pattern expansion
>>
>> Paulo Matos writes:
>> > On a vector processor w
> -Original Message-
> From: Richard Sandiford [mailto:rsand...@linux.vnet.ibm.com]
> Sent: 27 January 2014 16:50
> To: Paulo Matos
> Cc: gcc@gcc.gnu.org
> Subject: Re: Mode change for bswap pattern expansion
>
> Sorry, I meant we use an unspec for the first ("V2HI") rotate.
> I.e. rather
It is also available as hjl/linux/release/2.24.51.0.3 tag at
https://sourceware.org/git/?p=binutils-gdb.git;a=summary
H.J.
---
This is the beta release of binutils 2.24.51.0.3 for Linux, which is
based on binutils 2014 0127 master branch on sourceware.org plus
various changes. It is purely for L
On Jan 27, 2014, at 8:59 AM, Paulo Matos wrote:
>> -Original Message-
>> From: Richard Sandiford [mailto:rsand...@linux.vnet.ibm.com]
>> Sent: 27 January 2014 16:50
>> To: Paulo Matos
>> Cc: gcc@gcc.gnu.org
>> Subject: Re: Mode change for bswap pattern expansion
>>
>> Sorry, I meant we
Hello,
motivated by the recent MPC 1.0.2 announcement, I looked at
./contrib/download_prerequisites and also at
ftp://gcc.gnu.org/pub/gcc/infrastructure/ to see which versions are
offered there.
Question: Would it make sense to place newer versions into
infrastructure and update ./contrib/d
On 01/27/2014 08:29 PM, Tobias Burnus wrote:
Hello,
motivated by the recent MPC 1.0.2 announcement, I looked at
./contrib/download_prerequisites and also at
ftp://gcc.gnu.org/pub/gcc/infrastructure/ to see which versions are
offered there.
Question: Would it make sense to place newer versions i
On Sat, 2014-01-25 at 20:34 +, Richard Sandiford wrote:
> Yeah, I've been trying to use separate variables for new flags.
> That's why a lot of the MIPS options have discrete TARGET_… variables
> (defined via Var(TARGET_…)). target_flags should only really be needed
> for options whose defaul
On Mon, Jan 27, 2014 at 1:42 PM, H.J. Lu wrote:
> On Sat, Jan 18, 2014 at 8:11 AM, H.J. Lu wrote:
>> Hi,
>>
>> Here is the proposal to update x86-64 PLT for MPX. The linker change
>> is implemented on hjl/mpx/pltext8 branch. Any comments/feedbacks?
>>
>> Thanks.
>>
>> --
>> H.J.
>> ---
>> Intel
Steve Ellcey writes:
> On Sat, 2014-01-25 at 20:34 +, Richard Sandiford wrote:
>
>> Yeah, I've been trying to use separate variables for new flags.
>> That's why a lot of the MIPS options have discrete TARGET_… variables
>> (defined via Var(TARGET_…)). target_flags should only really be neede
This is on trunk - I was under the impression that it is always trunk,
unless otherwise stated?
getpid doesn't really make sense for bare metal targets, I would think?
Regards
Senthil
On Mon, Jan 27, 2014 at 01:04:48PM +, Umesh Kalappa wrote:
> Senthil,
> Please do let us know the gcc versio
18 matches
Mail list logo