I have now committed it as obvious.
The constraint, I couldn't find, was/is C546 (thanks to Reinhard Bader).
With coarrays, I tend to have the problem whether the best search term
is coarray or codimension (or sometimes also: coindexed, corank).
Committed as Rev. 212540
Tobias
Tobias Burnus
On Thu, Jul 10, 2014 at 12:57 AM, Paolo Carlini
wrote:
> On 07/10/2014 06:30 AM, Tim Shen wrote:
>>
>> Here's the sane patch :)
>
> Ok, thanks!
Tested and committed.
Thanks!
--
Regards,
Tim Shen
Hi,
When I try to print the dumps of fold-const.c
with -fdump-rtl-all-slim cc1plus crashes.
This is caused by pretty-printing the ADDR_VEC pattern,
which has a single argument, a vector of LABEL_REFs at position 0.
But instead XEXP(x,0) is printed, which causes the ICE.
However also ADDR_DIFF_VEC
On 14/07/14 14:11 -0600, Tom Tromey wrote:
Jonathan> I forgot to say that with these type recognizers we might want to
Jonathan> revisit the output of the existing printers for the containers, so
Jonathan> that instead of:
Jonathan> std::map with 3 elements = { ... }
Jonathan> GDB could print th
On 14/07/14 14:08 -0600, Tom Tromey wrote:
Jonathan> This passes the python testsuite but I'll wait for comments before
Jonathan> committing, in case my use of the GDB API or Python can be improved by
Jonathan> anyone.
It looked fine to me.
Thanks for checking it. One thing I should have menti
On Mon, Jul 14, 2014 at 2:37 PM, Andrew Pinski wrote:
> On Mon, Jul 14, 2014 at 1:40 PM, Dehao Chen wrote:
>> This patch replaces getline with fgets so that gcc builts fine in darwin.
>
>
> Why not add getline to libiberty instead? This patch causes a huge stack
> usage.
The callee is only cal
On Mon, Jul 14, 2014 at 1:40 PM, Dehao Chen wrote:
> This patch replaces getline with fgets so that gcc builts fine in darwin.
Why not add getline to libiberty instead? This patch causes a huge stack usage.
Thanks,
Andrew Pinski
>
> Testing on going, ok for google-4_9 if test passes?
>
> Than
On 07/11/2014 02:27 AM, Thomas Schwinge wrote:
> Hi Cesar!
>
> On Thu, 10 Jul 2014 11:47:42 -0700, Cesar Philippidis
> wrote:
>> These patch enables the collapse clause with a value greater than one.
>
> Thanks!
>
>> Is this patch OK for gomp-4_0-branch?
>
> OK with the following addressed:
>
On 07/11/2014 02:15 AM, Thomas Schwinge wrote:
> Hi Cesar!
>
> On Thu, 10 Jul 2014 11:43:11 -0700, Cesar Philippidis
> wrote:
>> This patch addresses two bugs openacc reduction clause bugs.
>
> Thanks! OK; one question/suggestion, though:
>
>> --- a/gcc/omp-low.c
>> +++ b/gcc/omp-low.c
>> @@
On 07/14/2014 05:12 PM, Paolo Carlini wrote:
Thanks. This helps me a lot. In particular I see now, in tsubst_arg_types:
/* Do array-to-pointer, function-to-pointer conversion, and ignore
top-level qualifiers as required. */
type = cv_unqualified (type_decays_to (type));
which
The problem in this testcase is that we inlined the decloned constructor
into the calling thunks, so it was removed by
symtab_remove_unreachable_nodes. verify_symtab sees that it is no
longer linked to the calling thunks with same_comdat_group and complains.
Here I've changed verify_symtab to
Hi,
On 07/14/2014 09:47 PM, Jason Merrill wrote:
On 07/14/2014 12:20 PM, Paolo Carlini wrote:
I have been looking a bit into this bug, using a reduced testcase which
simplifies the debugging quite a bit for me (a non-variadic variant is
ok). I cannot say to already understand all the details of
This patch replaces getline with fgets so that gcc builts fine in darwin.
Testing on going, ok for google-4_9 if test passes?
Thanks,
Dehao
Index: gcc/coverage.c
===
--- gcc/coverage.c (revision 212523)
+++ gcc/coverage.c (working c
When I fixed 56947 in 4.7, I added an assert to make sure that the trunk
was being sensible in the way I expected: local class member functions
are supposed to be instantiated from the TAG_DEFN. But we can get to
instantiate_decl before that if it's used from another local class
member functio
> "Jonathan" == Jonathan Wakely writes:
Jonathan> I forgot to say that with these type recognizers we might want to
Jonathan> revisit the output of the existing printers for the containers, so
Jonathan> that instead of:
Jonathan> std::map with 3 elements = { ... }
Jonathan> GDB could print t
On 14 July 2014 04:58:17 Kugan wrote:
On 11/07/14 22:47, Richard Biener wrote:
> On Fri, Jul 11, 2014 at 1:52 PM, Kugan
> wrote:
>> Thanks foe the review and suggestions.
>>
>> On 10/07/14 22:15, Richard Biener wrote:
>>> On Mon, Jul 7, 2014 at 8:55 AM, Kugan
wrote:
>>
>> [...]
>>
> "Jonathan" == Jonathan Wakely writes:
Jonathan> This defines a new style of Python type printer that
Jonathan> recognizes templates and can be used to omit default template
Jonathan> arguments from the typename GDB prints, e.g. showing
Jonathan> std::vector> as simply std::vector.
Jonathan>
I changed more than I should have. A slightly smaller patch.
dw
On 7/14/2014 12:31 AM, David Wohlferd wrote:
I have a release on file with the FSF, but don't have SVN write access.
Problem description:
gnat docs have warning messages when compiled with makeinfo 5.2. Most
of them revolve aro
While checking whether gfortran already handles the new constraint at
http://j3-fortran.org/doc/year/14/14-140r2.txt (it does), I found the
following issues:
a) Coarray variables with pointer attribute weren't rejected.
b) There was a copy'n'paste error in symbol.c, having cray_pointer at
plac
On Mon, Jul 14, 2014 at 10:09 AM, Maxim Kuvyrkov wrote:
> On Jul 14, 2014, at 8:05 PM, Steven Bosscher wrote:
>
>> On Mon, Jul 14, 2014 at 6:12 AM, Maxim Kuvyrkov wrote:
>>> Hi,
>>>
>>> This patch fixes 2 of the [several] problems in rank_for_schedule
>>> heuristics for SCHED_PRESSURE_MODEL. SCHE
Dear Tobias,
It looks OK to me - good for trunk
Thanks for the patch
Paul
On 14 July 2014 19:19, Tobias Burnus wrote:
> If the atomic_ref VALUE argument is of a different kind than the ATOM
> argument, the result was wrong with -fcoarray=lib. That showed up with
> gfortran.dg/coarray/atomic_1.
> "Mark" == Mark Wielaard writes:
Hi Mark.
Mark> The following two patches are based on the earlier "dwarf2out.c: Pass
Mark> one cv_quals argument" and "Emit DW_tag_restrict_type" patches I posted
Mark> earlier. Since there currently is not even an early draft yet for DWARFv5,
Mark> just a c
On Thu, Jul 3, 2014 at 3:38 PM, Ilya Enkovich wrote:
> 2014-07-03 16:07 GMT+04:00 Uros Bizjak :
>> On Thu, Jul 3, 2014 at 1:50 PM, Ilya Enkovich wrote:
>>
>>> I didn't find a nice way to fix peephole2 patterns to take register
>>> constraints into account. Is there any way to do it?
>>
>> Use REX
S, Pitchumani schrieb:
Attached patch changes the device name macro of two rev devices, from REV
to rev in the name.
Device name macro:
__AVR_ATmega16HVBREVB__
__AVR_ATmega32HVBREVB__
Change to:
__AVR_ATmega16HVBrevB__
__AVR_ATmega32HVBrevB__
'rev' in small letters emphasizes the revision of t
On 07/14/2014 12:20 PM, Paolo Carlini wrote:
I have been looking a bit into this bug, using a reduced testcase which
simplifies the debugging quite a bit for me (a non-variadic variant is
ok). I cannot say to already understand all the details of the issue,
but something which strikes me as inter
This is another patch for the python printers, so the diff is relative
to my patch from earlier today, but it's actually independent.
This adds printers for the types in the std::experimental namespace.
For 'any' and 'optional' the printer will say "no contained value"
when that's the case, othe
On 14/07/14 15:21 +0100, Jonathan Wakely wrote:
This defines a new style of Python type printer that recognizes
templates and can be used to omit default template arguments from the
typename GDB prints, e.g. showing std::vector> as
simply std::vector. Additionally, T will get processed by the ty
[ Sorry, re-sending with fixed email address. ]
Hello,
this is an attempt to update the prior patch:
https://gcc.gnu.org/ml/gcc-patches/2014-07/msg00635.html
to add a -Wpsabi note as discussed.
However, this is causing a bit of difficulties. First of all, the warning
triggers in a larger numbe
Hello,
this is an attempt to update the prior patch:
https://gcc.gnu.org/ml/gcc-patches/2014-07/msg00635.html
to add a -Wpsabi note as discussed.
However, this is causing a bit of difficulties. First of all, the warning
triggers in a larger number of tests -- which was probably to be expected
si
Hello,
this patch updates the prior version:
https://gcc.gnu.org/ml/gcc-patches/2014-07/msg00634.html
to add a -Wpsabi note as discussed.
Note that the warning triggers whenever type is encountered whose alignment
*requirement* changes due to this patch. In some cases, this does not actually
cha
Hello,
this patch updates the prior version:
https://gcc.gnu.org/ml/gcc-patches/2014-07/msg00632.html
to add a -Wpsabi note as discussed.
(We may need to change the "GCC 4.10" string if the next release turns out
to get a different name ...)
In a testsuite run, this note triggers only in those t
On Mon, Jul 14, 2014 at 5:36 PM, Richard Biener
wrote:
> On Fri, Jul 11, 2014 at 4:59 PM, Prathamesh Kulkarni
> wrote:
>> On 7/11/14, Richard Biener wrote:
>>> On Thu, Jul 10, 2014 at 8:05 PM, Prathamesh Kulkarni
>>> wrote:
Hi,
I have attempted to add syntax for symbol to denote mu
Committed to branch dmalcolm/jit:
Certain client code that repeatedly performed in-process compilations with
optimizations and inlinable functions led to a segfault within
ipa-cp.c:propagate_effects, whilst traversing the values_topo list.
The root cause was that values_topo was not reset to NULL
If the atomic_ref VALUE argument is of a different kind than the ATOM
argument, the result was wrong with -fcoarray=lib. That showed up with
gfortran.dg/coarray/atomic_1.f90 - but for some reasons only with -m32.
The fix is to create a temporary variable in this case, what the patch does.
OK fo
Committed the following to branch dmalcolm/jit:
Investigating a bug in a project using libgccjit revealed a problem where
fields within a struct within the JIT-created code weren't laid out in the
same places as the supposedly same struct in normally-built code:
struct foo
{
int a;
in
Hello
On 07/11/2014 12:07 PM, Jan Hubicka wrote:
Hi,
this first patch continues with rafactoring of IPA infrastructure so that
we will have C++ API. In the patch, I transformed many global functions to
members of symtab_node and cgraph_node.
Example:
cgraph_remove_node (struct cgraph_node
Hi,
I have been looking a bit into this bug, using a reduced testcase which
simplifies the debugging quite a bit for me (a non-variadic variant is
ok). I cannot say to already understand all the details of the issue,
but something which strikes me as interesting, is that the DEDUCE_CALL
passe
On 14/07/14 15:34, Richard Earnshaw wrote:
Noticed while browsing the code. The add_losym_ instruction takes
an immediate field as the third operand. Hence it's type is alu_imm,
not alu_reg.
Probably doesn't have any major effect on current pipeline models, but
could do one day...
Committed
> On 06/25/2014 02:51 AM, Jan Hubicka wrote:
> >@@ -4388,7 +4388,8 @@ build_clone (tree fn, tree name)
> >clone = copy_decl (fn);
> >/* Reset the function name. */
> >DECL_NAME (clone) = name;
> >- SET_DECL_ASSEMBLER_NAME (clone, NULL_TREE);
> >+ if (TREE_CODE (clone) != TEMPLATE_DEC
> On Mon, Jul 14, 2014 at 09:50:34AM -0400, Jason Merrill wrote:
> > >>/daten/aranym/gcc/gcc-20140714/gcc/testsuite/g++.dg/cpp0x/static_assert9.C:5:1:
> > >> error: non-constant condition for static assertion
> > >>/daten/aranym/gcc/gcc-20140714/gcc/test
Noticed while browsing the code. The add_losym_ instruction takes
an immediate field as the third operand. Hence it's type is alu_imm,
not alu_reg.
Probably doesn't have any major effect on current pipeline models, but
could do one day...
Committed to trunk.
2014-07-14 Richard Earnshaw
This defines a new style of Python type printer that recognizes
templates and can be used to omit default template arguments from the
typename GDB prints, e.g. showing std::vector> as
simply std::vector. Additionally, T will get processed by the type
recognizers so if it's a standard typedef or t
Ping
2014-07-03 17:38 GMT+04:00 Ilya Enkovich :
> 2014-07-03 16:07 GMT+04:00 Uros Bizjak :
>> On Thu, Jul 3, 2014 at 1:50 PM, Ilya Enkovich wrote:
>>
>>> I didn't find a nice way to fix peephole2 patterns to take register
>>> constraints into account. Is there any way to do it?
>>
>> Use REX_SSE_
On Mon, Jul 14, 2014 at 09:50:34AM -0400, Jason Merrill wrote:
> >>/daten/aranym/gcc/gcc-20140714/gcc/testsuite/g++.dg/cpp0x/static_assert9.C:5:1:
> >> error: non-constant condition for static assertion
> >>/daten/aranym/gcc/gcc-20140714/gcc/testsuite/g++.dg/cpp0x/stati
On 06/25/2014 02:51 AM, Jan Hubicka wrote:
@@ -4388,7 +4388,8 @@ build_clone (tree fn, tree name)
clone = copy_decl (fn);
/* Reset the function name. */
DECL_NAME (clone) = name;
- SET_DECL_ASSEMBLER_NAME (clone, NULL_TREE);
+ if (TREE_CODE (clone) != TEMPLATE_DECL)
+SET_DECL_A
On 07/14/2014 04:36 AM, Jan Hubicka wrote:
FAIL: g++.dg/cpp0x/static_assert9.C -std=c++11 (test for excess errors)
Excess errors:
/daten/aranym/gcc/gcc-20140714/gcc/testsuite/g++.dg/cpp0x/static_assert9.C:5:1:
error: non-constant condition for static assertion
/daten/aranym/gcc/gcc-20140714
The following makes copyprop simplify conditions properly (it's
now also copy-propagating constants, thus more opportunities
arise). That fixes the testcase which previously failed to
constant-propagate the __builtin_constant_p result into the asm.
Bootstrapped and tested on x86_64-unknown-linux
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied.
Richard.
2014-07-14 Richard Biener
* libgcov.h (struct gcov_fn_info): Make ctrs size 1.
Index: libgcc/libgcov.h
===
--- libgcc/libgcov.h(revision 212515)
On Mon, Jul 14, 2014 at 12:16 PM, Yuri Rumyantsev wrote:
> Ping!
It's in my queue (pretty large patch for a drive-by review - maybe there is
an opportunity to split the patch up?).
Won't get to it before the Cauldron though.
Richard.
> 2014-06-25 18:06 GMT+04:00 Yuri Rumyantsev :
>> Hi All,
>>
Attached patch changes the device name macro of two rev devices, from REV
to rev in the name.
Device name macro:
__AVR_ATmega16HVBREVB__
__AVR_ATmega32HVBREVB__
Change to:
__AVR_ATmega16HVBrevB__
__AVR_ATmega32HVBrevB__
'rev' in small letters emphasizes the revision of the device.
If OK, could
On Sun, Jul 13, 2014 at 7:23 PM, Prathamesh Kulkarni
wrote:
> Hi,
>This patch uses integral_op_p instead of
> if (INTEGRAL_TYPE_P (TREE_TYPE (@0)))
>
> * match.pd: Remove INTEGRAL_TYPE_P (TREE_TYPE (@0)) in bitwise
> patterns and use integral_op_p@0
Hmm, so this removes if-exprs and instead u
On Sun, Jul 13, 2014 at 2:31 PM, Prathamesh Kulkarni
wrote:
> This patch adds DEBUG_FUNCTION attribute to print_* functions
> in genmatch.c
Thanks, applied.
Richard.
> * genmatch.c (print_operand): Add attribute DEBUG_FUNCTION.
> (print_matches): Likewise.
> (decision_tree::print_node): Lik
On Fri, Jul 11, 2014 at 4:59 PM, Prathamesh Kulkarni
wrote:
> On 7/11/14, Richard Biener wrote:
>> On Thu, Jul 10, 2014 at 8:05 PM, Prathamesh Kulkarni
>> wrote:
>>> Hi,
>>>I have attempted to add syntax for symbol to denote multiple
>>> operators.
>>>
>>> I tried it with few bogus patterns
On Sun, Jul 13, 2014 at 07:55:44PM +0200, Marek Polacek wrote:
> 2014-07-13 Marek Polacek
>
> * ubsan.h (struct ubsan_mismatch_data):
Missing description.
> +/* Expand UBSAN_OBJECT_SIZE internal call. */
> +
> +void
> +ubsan_expand_objsize_ifn (gimple_stmt_iterator *gsi)
> +{
> + gim
> -Original Message-
> From: gcc-patches-ow...@gcc.gnu.org [mailto:gcc-patches-ow...@gcc.gnu.org]
> On Behalf Of Denis Chertykov
> Sent: Friday, July 11, 2014 9:53 PM
> To: S, Pitchumani
> Cc: gcc-patches@gcc.gnu.org; Georg-Johann Lay
> Subject: Re: [Patch, avr] Add atmel ata5782 and ata583
LEON3 has a store buffer of length 1, so an additional store is required
to be sure that the one preceding it has been written to memory. I am
not familiar enough with the internals of gcc to pick the optimal place
to encode this behavior, so any suggestions from you are appreciated :)
On 2014
Fixed by the PR61757 fix.
Richard.
2014-06-14 Richard Biener
PR tree-optimization/61786
* gcc.dg/torture/pr61786.c: New testcase.
* gcc.dg/lto/pr61786_0.c: Likewise.
* gcc.dg/lto/pr61786_1.c: Likewise.
Index: gcc/testsuite/gcc.dg/torture/pr61786.c
===
On Mon, 14 Jul 2014, Richard Biener wrote:
> On Fri, 11 Jul 2014, Jakub Jelinek wrote:
>
> > On Fri, Jul 11, 2014 at 03:36:15PM +0200, Richard Biener wrote:
> > > *** c_strlen (tree src, int only_value)
> > > *** 606,612
> > >
> > > /* If the offset is known to be out of b
On 05/07/14 21:20, Rainer Orth wrote:
Rainer Orth writes:
Roman Gareev writes:
It seems the patch1/patch2 files you attach have the Content-Type:
application/octet-stream. This makes it impossible to view them inline.
Could you send them as text files? Just calling them patch1.patch or
pat
> I've checked in a patch to save the _M_n state.
If it is r212496, did you test it?
It breaks many tests (see
https://gcc.gnu.org/ml/gcc-regression/2014-07/msg00213.html)
/opt/gcc/work/libstdc++-v3/include/ext/random.tcc: In function
'std::basic_ostream<_CharT, _Traits>&
__gnu_cxx::operator<
"Jürgen Urban" writes:
> The problem happens with the r5900 hard float configurations, e.g.:
> configure --target=mipsel-linux-gnu --with-float=hard --with-fpu=single
> --with-arch=r5900
> I created the attached patch which fixes this problem for r5900 and
> another problem explained later.
> The
Ping!
2014-06-25 18:06 GMT+04:00 Yuri Rumyantsev :
> Hi All,
>
> We implemented additional support for pragma omp simd in part of
> extended if-conversion loops with such pragma. These extensions
> include:
>
> 1. All extensions are performed only if considered loop or its outer
>loop was mark
On 14/07/14 11:04, Kyrill Tkachov wrote:
> Hi all,
>
> I noticed that we don't have scheduling information for the clz and rbit
> instructions in any of the arm pipeline
> models except the Cortex-A8 one.
>
> This patch adds those insn types to the relevant models. They're treated
> as simple A
currently the following testcases are disabled for arm target,
gcc.dg/ira-shrinkwrap-prep-1.c
gcc.dg/ira-shrinkwrap-prep-2.c
gcc.dg/pr10474.c
the reason is on arm target, register r3 is caller-saved. Normally it does
not need to be saved on entry by the prologue. However if we choose to sav
On Fri, Jul 11, 2014 at 6:41 PM, Gaius Mulley
wrote:
>
>
> Hello,
>
> I've been looking through tree-ssa-loop-im.c (while hunting down a bug
> in the modula-2 front end) and found a curiosity in
> gcc/tree-ssa-loop-im.c.
>
> It seems that there is dead code in function determine_max_movement
> as
Hi all,
I noticed that we don't have scheduling information for the clz and rbit
instructions in any of the arm pipeline
models except the Cortex-A8 one.
This patch adds those insn types to the relevant models. They're treated
as simple ALU operations.
Tested arm-none-eabi.
Ok for trunk?
On 11/07/14 14:20, Alexander Monakov wrote:
On Fri, 11 Jul 2014, Kyrill Tkachov wrote:
On 10/07/14 22:53, Maxim Kuvyrkov wrote:
The patch looks good to me, but some cleanup suggestions below.
Thanks, here's an updated patch.
How's this?
You need to remove 'if (targetm. ...) SCHED_GROUP_P (in
Committed as obvious.
Richard.
2014-07-14 Richard Biener
* cgraph.h (decl_in_symtab_p): Make inline.
Index: gcc/cgraph.h
===
--- gcc/cgraph.h(revision 212510)
+++ gcc/cgraph.h(working copy)
@@ -1154,7 +1
The following reverts the proper part of the loop depth dependent
copy-propagation restriction patch. The canonicalization that
record_equality does is important for correctness when threading
over backedges (that must be accidential? I can't see how it
might not be possible to trigger this with
On Tue, 8 Jul 2014, Gerald Pfeifer wrote:
> A couple of us noticed, over time, that our instructions on who
> can sponsor SVN write access and how to get it are not as clear
> as they could be. This tries to improve that.
Further clarifications and strengthening the "Else" part based
on feedback
On Mon, Jul 14, 2014 at 12:39 AM, Jerry DeLisle wrote:
> Hi all,
>
> This bug was caused by an access to an invalid pointer offset to the format
> string. This was only a problem on the second error using the same format
> string. I suspect it has to do with caching the format strings. Regardles
On 14 July 2014 09:45, Marat Zakirov wrote:
> Unfortunately, I didn't reproduce the issue...
>
> Could you please provide full info? Including gcc trunk version, configure
> line, failed test command line.
>
> Thank you.
>
I'm not at office, so I am not going to be able to provide full details.
Ho
> Hi,
> this patch moves DECL_ARGUMENTS into FUNCTION_DECL. For this I needed to
> solve
> reuse in C++ and objC frontends. In C++ I think I actually run out of places
> to use for TEMPLATE_DECL (well, perhaps DECL_ATTRIBUTES but I would definitely
> run out of pointers fro DECL_RESULT I want to
t; > * g++.dg/tree-ssa/nonzero-2.C: New testcase.
> > * g++.dg/tree-ssa/nonzero-1.C: New testcase.
> > * gcc.dg/tree-ssa/nonzero-1.c: New testcase.
>
> FAIL: g++.dg/cpp0x/static_assert9.C -std=c++11 (test for excess errors)
> Excess errors:
> /daten/aranym/
testcase.
> * g++.dg/tree-ssa/nonzero-1.C: New testcase.
> * gcc.dg/tree-ssa/nonzero-1.c: New testcase.
FAIL: g++.dg/cpp0x/static_assert9.C -std=c++11 (test for excess errors)
Excess errors:
/daten/aranym/gcc/gcc-20140714/gcc/testsuite/g++.dg/cpp0x/static_assert9.C:5:1:
error: n
Hi,
On 07/14/2014 09:58 AM, Andreas Schwab wrote:
FAIL: ext/random/arcsine_distribution/cons/default.cc (test for excess errors)
Excess errors:
/daten/aranym/gcc/gcc-20140714/libstdc++-v3/include/ext/random.tcc:1587:22:
error: '_M_n' was not declared in this scope
/daten/aran
On Mon, Jul 14, 2014 at 10:05 AM, Kyrill Tkachov wrote:
>> Attached patch optimizes ix86_atomic_assign_expand_fenv by using
>> register form of "fnstsw %ax" instead of "fnstsw ". This way a
>> memory RW cycle is removed for a temporary.
>
> The patch you attached seems to be the hook implementati
On Jul 14, 2014, at 8:05 PM, Steven Bosscher wrote:
> On Mon, Jul 14, 2014 at 6:12 AM, Maxim Kuvyrkov wrote:
>> Hi,
>>
>> This patch fixes 2 of the [several] problems in rank_for_schedule heuristics
>> for SCHED_PRESSURE_MODEL. SCHED_PRESSURE_MODEL is used for first scheduling
>> pass in ARM
On 12/07/14 10:07, Uros Bizjak wrote:
Hello!
Attached patch optimizes ix86_atomic_assign_expand_fenv by using
register form of "fnstsw %ax" instead of "fnstsw ". This way a
memory RW cycle is removed for a temporary.
Hi Uros,
The patch you attached seems to be the hook implementation for alp
On Mon, Jul 14, 2014 at 6:12 AM, Maxim Kuvyrkov wrote:
> Hi,
>
> This patch fixes 2 of the [several] problems in rank_for_schedule heuristics
> for SCHED_PRESSURE_MODEL. SCHED_PRESSURE_MODEL is used for first scheduling
> pass in ARM backend by default.
>
> The first one is when INSN_TICK of bot
FAIL: ext/random/arcsine_distribution/cons/default.cc (test for excess errors)
Excess errors:
/daten/aranym/gcc/gcc-20140714/libstdc++-v3/include/ext/random.tcc:1587:22:
error: '_M_n' was not declared in this scope
/daten/aranym/gcc/gcc-20140714/libstdc++-v3/include/ext/random.tcc:1598:
On Fri, 11 Jul 2014, Jakub Jelinek wrote:
> On Fri, Jul 11, 2014 at 03:36:15PM +0200, Richard Biener wrote:
> > *** c_strlen (tree src, int only_value)
> > *** 606,612
> >
> > /* If the offset is known to be out of bounds, warn, and call strlen at
> >runtime. */
>
Unfortunately, I didn't reproduce the issue...
Could you please provide full info? Including gcc trunk version,
configure line, failed test command line.
Thank you.
--Marat
On 07/11/2014 11:19 PM, Christophe Lyon wrote:
The new testcase causes an ICE when the compile is configured
--with-th
I have a release on file with the FSF, but don't have SVN write access.
Problem description:
gnat docs have warning messages when compiled with makeinfo 5.2. Most
of them revolve around the fact that nodes must be defined in the same
order as they appear in menus.
ChangeLog:
2014-07-14 Davi
Eric, here are the ada doc modifications we discussed. I believe I have
addressed the rest of the items that concerned you. While I have a
release on file with the FSF, I do not have SVN write permissions.
Problem description:
The modifications to the c inline asm docs (extend.texi) necessita
85 matches
Mail list logo
