On 2014-02-21 15:49, Jason Merrill wrote:
On 02/21/2014 03:19 AM, Adam Butcher wrote:
Jason Merrill wrote:
Why doesn't num_template_parameter_lists work as a predicate here?
It works in the lambda case as it is updated there, but for generic
functions I think the following prevents it:
cp
Hello,
looking at this question:
http://stackoverflow.com/q/21737186/1918193
I was surprised to see that libstdc++'s std::complex basically just works
with user-defined types, even weird expression template ones, although
that's not a supported use afaik.
The only functions that fail seem to
Hello,
a natural first step to optimize changes of rounding modes seems to be
making these 2 functions builtins. I don't know exactly how far
optimizations will be able to go (the fact that fesetround can fail
complicates things a lot). What is included here:
1) fegetround is pure.
2) Neith
Hi,
the test case gfortran.dg/vect/pr32380.f was found to fail on
armv7l-unknown-linux-gnueabihf.
The reason for this is that one out of 6 loops does not get vectorized, because
this target does
not support a vectorization of sqrtf.
The same test case is known to fail on powerpc-apple-darwin9 d
On 02/23/2014 11:32 AM, Marc Glisse wrote:
Hello,
looking at this question:
http://stackoverflow.com/q/21737186/1918193
I was surprised to see that libstdc++'s std::complex basically just
works with user-defined types, even weird expression template ones,
although that's not a supported use af
On Sun, 23 Feb 2014, Paolo Carlini wrote:
On 02/23/2014 11:32 AM, Marc Glisse wrote:
Hello,
looking at this question:
http://stackoverflow.com/q/21737186/1918193
I was surprised to see that libstdc++'s std::complex basically just works
with user-defined types, even weird expression template o
On Sat, Feb 22, 2014 at 10:25 PM, Bill Schmidt
wrote:
> Hi,
>
> This patch adds -maltivec=be support for vec_lde and vec_ste, similarly
> to what was done for vec_ld, vec_st, vec_ldl, and vec_stl. Much of the
> same infrastructure is used. Because the insn pattern for vec_ste is
> formed slightl
This is not really a regression but, in the light of the recent discussion
about VIEW_CONVERT_EXPRs, I think this is worth having in 4.9: we can fold
more VIEW_CONVERT_EXPRs internally generated in gigi.
Tested on x86_64-suse-linux, applied on the mainline.
2014-02-23 Eric Botcazou
Hi,
There's an assert in rs6000_emit_le_vsx_move () that was correct for
-mcpu=power7, but with the TImode changes for Power8, we can trigger the
assert with -mcpu=power8 on little endian. We can now see a dest rtx
that is a vector subreg of TImode. Allowing for this in the assert
fixes a failur
On 02/14/14 09:41, Michael Eager wrote:
On 02/13/14 21:48, David Holsgrove wrote:
Hi Michael,
-Original Message-
From: Michael Eager [mailto:ea...@eagerm.com]
Sent: Sunday, 26 January 2014 1:57 am
To: David Holsgrove
Cc: gcc-patches@gcc.gnu.org; Edgar Iglesias; John Williams; Vinod Kat
On 02/14/14 09:42, Michael Eager wrote:
On 02/13/14 21:48, David Holsgrove wrote:
Hi Michael, List,
-Original Message-
From: David Holsgrove
Sent: Wednesday, 22 January 2014 1:43 pm
To: 'Michael Eager'; gcc-patches@gcc.gnu.org
Cc: Edgar Iglesias; John Williams; Vidhumouli Hunsigida; Na
On 11/25/13 23:53, David Holsgrove wrote:
Hi Michael,
I've attached patch based on latest gcc master. Please apply when ready.
Changelog
2013-11-26 David Holsgrove
* gcc/config/microblaze/predicates.md: Add cmp_op predicate.
* gcc/config/microblaze/microblaze.md: Add branch_compare
On 11/25/13 23:53, David Holsgrove wrote:
Existing MicroBlaze shift instruction pattern names don't match
surrounding format.
ashlri_reg should be ashrsi_reg - arithmetic shift right for SI mode
lshlri_reg should be lshrsi_reg - logical shift right for SI mode
Changelog
2013-11-26 David Holsg
Ahem, patch resubmitted with the testsuite correctly adjusted this
time. Tested x86_64 linux, still OK to commit ?
2014-02-23 Fabien Chene
PR c++/52369
* cp/method.c (walk_field_subobs): improve the diagnostic
locations for both REFERENCE_TYPEs and non-static const members.
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'gcc' has been submitted
by the Swedish team of translators. The file is available at:
http://translationproject.org/latest/gcc/sv.po
(This file, 'gcc-4.9-b20140202.sv.po',
I noticed in passing that this 4.7 cleanup:
http://article.gmane.org/gmane.comp.gcc.patches/224853
changed caller-save.c:add_used_regs_1 from:
if (REG_P (x))
{
regno = REGNO (x);
if (!HARD_REGISTER_NUM_P (regno))
regno = reg_renumber[regno];
if (regno >= 0)
On Sun, Feb 23, 2014 at 10:14 PM, Richard Sandiford wrote:
> I noticed in passing that this 4.7 cleanup:
>
> http://article.gmane.org/gmane.comp.gcc.patches/224853
...
> so that nothing happens for pseudos. I've no idea whether this makes
> a difference in practice or not but it seems safer to r
Hi everyone,
no comments for my patch?
于 2014年02月21日 10:43, lin zuojian 写道:
> Hi,
> I have misunderstood the meaning of STRICT_ALIGNMENT.Sorry for that Jakub.
> I think patch v2 have modified as Jakub suggested.
>
>
> ---
> Without aligning the asan stack base,this base will only 64-bit aligned
>
Hi,
The following patch fixes two issues: the first is PR c++/25940 and the second
is related to PR c++/13699.
The first issue is that the C++ frontend fails to reject duplicate definitions
of functions with C language linkage. This results in the compiler emitting
ASM that defines the same symb
Hi
The following patch fixes an obvious wrong index used to access the
dense array. The patch has passed the bootstrap and regression tests
on x86-64.
OK for trunk?
thanks
Carrot
2014-02-23 Guozhi Wei
* sparseset.h (sparseset_pop): Fix the wrong index.
Index: sparseset.h
20 matches
Mail list logo
