On Wednesday 2015-01-14 17:56, Chung-Ju Wu wrote:
> 2015-01-14 Chung-Ju Wu
>
> * doc/invoke.texi (NDS32 Options): Add -mcmodel= option and
> remove -mgp-direct option.
>
> Although these changes are target-specific part, I think it would be better
> for others to have review com
On Wednesday 2015-01-14 17:58, Chung-Ju Wu wrote:
> 2015-01-14 Chung-Ju Wu
>
> * doc/invoke.texi (NDS32 Options): Remove -mforce-fp-as-gp,
> -mforbid-fp-as-gp, and -mex9 options.
Can you cover these, and similar changes, in the release notes
at htdocs/gcc-5/changes.html, please
On Saturday 2015-01-17 13:55, Sandra Loosemore wrote:
> 2015-01-17 Sandra Loosemore
>
> gcc/
> * doc/invoke.texi ([-ftracer]): Remove duplicate option listing.
Thanks for doing these cleanups, Sandra.
The attachment only had the ChangeLog, not the patch. Since I had
a look anyway
On Sat, Jan 17, 2015 at 7:36 PM, Rainer Orth
wrote:
> Uros Bizjak writes:
>
>> On Sat, Jan 17, 2015 at 4:18 PM, Rainer Orth
>> wrote:
>>
The patch removes EBX usage from asm code used in libgcc/crtstuff.c
It is safe now, but potentially buggy when glibc is rebuild with GCC
5.0 as
Hi all,
the attached patch is close to trivial and fixes a memory-leak
regression that appeared after the implementation of finalization.
My suspicion it that it's simply a copy'n'paste error, where the wrong
attribute was copied from very similar code a few lines above, but I'd
like to have that
On Fri, Jan 16, 2015 at 04:04:27PM +0100, Martin Liška wrote:
> Hello.
>
> This patch adds support for __attribute__((no_icf)) that prevents a function
> being merged with a different one.
>
> Tested on x86_64-linux-pc.
>
> Ready for trunk?
> Thanks,
> Martin
> From 234fc8018f9810e2adf6d975d6d0
On Sat, 2015-01-17 at 22:40 +0900, Kaz Kojima wrote:
> Oleg Endo wrote:
> > Kaz, could you please test the patch on your sh4-linux setup and report
> > your findings? Even though it's a bit late, I'd like to get this in for
> > GCC 5, if it doesn't break too many things.
>
> Looks wrong code pro
On 17/01/15 19:51 -0700, Sandra Loosemore wrote:
On 01/17/2015 03:58 PM, Jonathan Wakely wrote:
My fault, this additional chunk is needed alongside the patch I sent
earlier:
--- a/libstdc++-v3/include/bits/atomic_futex.h
+++ b/libstdc++-v3/include/bits/atomic_futex.h
@@ -35,7 +35,7 @@
#include
On 18/01/15 13:19 +, Jonathan Wakely wrote:
On 17/01/15 19:51 -0700, Sandra Loosemore wrote:
On 01/17/2015 03:58 PM, Jonathan Wakely wrote:
My fault, this additional chunk is needed alongside the patch I sent
earlier:
--- a/libstdc++-v3/include/bits/atomic_futex.h
+++ b/libstdc++-v3/inclu
On 16/01/15 18:00 +0100, Torvald Riegel wrote:
+namespace std _GLIBCXX_VISIBILITY(default)
+{
+_GLIBCXX_BEGIN_NAMESPACE_VERSION
+
+ bool
+ __atomic_futex_unsigned_base::_M_futex_wait_until(unsigned *__addr,
+ unsigned __val,
+ bool __has_timeout, chrono::seconds __s, chrono::nanosecon
Hi Olivier,
On Thursday 2014-09-18 12:36, Olivier Hainque wrote:
> We have been maintaining a port to VxWorks MILS for powerpc for a while now
> and thought others might be interested.
>
> VxWorksMILS is very close to VxWorksAE, so the patch is pretty small. The main
> noticeable difference is th
Dear All,
Andre's patch for PR60357 did not fix this PR as we had hoped. The fix
needed is trivial, nay 'obvious'.
The problem was that a deep copy was not being performed; just an
assignement of the pointers to the data. In consequence the testcase
was being clobbered with a double free in the '
I have no idea why the C++11 status table says we're missing offsetof,
so I've removed that remark with this patch.
Committed to trunk.
commit c0783cfb57885eb5bd10bc52184872c5fae1a709
Author: Jonathan Wakely
Date: Sun Jan 18 15:46:23 2015 +
* doc/xml/manual/status_cxx2011.xml: Remove
Fix a past-the-end dereference in the new C++14 version of
is_permutation. This only affects C++14 mode, but fixes a new function
that exists entirely because it's meant to be safer than the C++98
version ... but it isn't safer if it goes past-the-end!
Tested x86_64-linux, committed to 4.9 and tr
Hi,
the testcase shows a case where try_make_edge_direct_virtual_call disagrees with
ipa_get_indirect_edge_target_1 making ipa-inline-transform to ICE on mismatch.
Bootstrapped/regtested x86_64-linux, comitted.
Honza
Index: ChangeLog
==
Hi,
this is variant I comitted after further testing. Main change is in
ipa-reference that can not
treat -fno-ipa-reference functions as external functions, because unlike those
they may affect
local variables.
Bootstrapped/regtested x86_64-linux, comitted.
Honza
* gcc.dg/ipa/ipa-icf-
On Sun, Jan 18, 2015 at 06:45:03PM +0100, Jan Hubicka wrote:
> @@ -1299,7 +1299,7 @@ has finished
>
> ; This option is not documented yet as its semantics will change.
> fgraphite
> -Common Report Var(flag_graphite)
> +Common Report Var(flag_graphite) Opitmization
> Enable in and out of Graphi
> On Sun, Jan 18, 2015 at 06:45:03PM +0100, Jan Hubicka wrote:
> > @@ -1299,7 +1299,7 @@ has finished
> >
> > ; This option is not documented yet as its semantics will change.
> > fgraphite
> > -Common Report Var(flag_graphite)
> > +Common Report Var(flag_graphite) Opitmization
> > Enable in a
Hi,
The attached patch fixes PR 64652. Tested with
make -k check-gcc RUNTESTFLAGS="sh-torture.exp --target_board=sh-sim
\{-m2/-ml,-m2/-mb,-m2a/-mb,-m4/-ml,-m4/-mb,-m4a/-ml,-m4a/-mb}"
Committed as r219824.
Cheers,
Oleg
gcc/ChangeLog:
PR target/64652
* config/sh/sh.md (udivsi3_i4,
On 16 January 2015 at 11:54, Marcus Shawcroft
wrote:
> On 15 January 2015 at 18:18, Richard Henderson wrote:
>> On 12/15/2014 12:41 AM, Zhenqiang Chen wrote:
>>> +(define_expand "cmp"
>>> + [(set (match_operand 0 "cc_register" "")
>>> +(match_operator:CC 1 "aarch64_comparison_operator"
>
On Sun, Jan 18, 2015 at 11:58 AM, Christophe Lyon
wrote:
> On 16 January 2015 at 11:54, Marcus Shawcroft
> wrote:
>> On 15 January 2015 at 18:18, Richard Henderson wrote:
>>> On 12/15/2014 12:41 AM, Zhenqiang Chen wrote:
+(define_expand "cmp"
+ [(set (match_operand 0 "cc_register" "")
On 18 January 2015 at 21:22, Andrew Pinski wrote:
> On Sun, Jan 18, 2015 at 11:58 AM, Christophe Lyon
> wrote:
>> On 16 January 2015 at 11:54, Marcus Shawcroft
>> wrote:
>>> On 15 January 2015 at 18:18, Richard Henderson wrote:
On 12/15/2014 12:41 AM, Zhenqiang Chen wrote:
> +(define_e
On Sat, 17 Jan 2015, Jakub Jelinek wrote:
> On Sat, Jan 17, 2015 at 01:18:44PM -0500, Hans-Peter Nilsson wrote:
> > (Waking up an old thread with my 2 cents due to being a little
> > behind on reading...)
> >
> > On Sat, 6 Dec 2014, Jakub Jelinek wrote:
> > > On Sat, Dec 06, 2014 at 09:28:57AM +010
This patch implements the free functions std::cbegin, std::cend,
std::rbegin, std::rend, std::crbegin and std::crend, which were
missing from our C++14 iterator library. I have run the added test
manually but I haven't finished running the full testsuite yet. I will
send the patch now anyway, if th
On Sat, Jan 17, 2015 at 01:18:44PM -0500, Hans-Peter Nilsson wrote:
> The current cc-first order happened more of an accidental
> opinion than an architectural decision as I vaguely recall, when
> asking. We also have the canonical location of a *cc clobber*,
> i.e. last in a parallel. For that r
On Sat, Jan 17, 2015 at 09:18:14PM -0500, David Edelsohn wrote:
> Supporting this turned out to be more involved. --with-cpu implicitly
> adds -mcpu to all specs, which invokes the assembler with the correct
> option. Directly setting TARGET_DEFAULT does not adjust the assembler
> invocation.
Si
On Sun, Jan 18, 2015 at 04:26:27PM -0500, Hans-Peter Nilsson wrote:
> For targets where most insns set condition-codes (and that don't
> use the deprecated CC0-machinery), those insns will always be
> expressed using a parallel with (most often) two members, one
> being the "main" part of the insn
On 19 January 2015 at 00:11, Ville Voutilainen
wrote:
> This patch implements the free functions std::cbegin, std::cend,
> std::rbegin, std::rend, std::crbegin and std::crend, which were
> missing from our C++14 iterator library. I have run the added test
> manually but I haven't finished running
On Sat, Jan 17, 2015 at 2:42 PM, Richard Henderson wrote:
>
> I tested non-support of libffi go closures before applying the patches
> for them for ppc, but I guess I busted something in the meantime.
>
> Please try this.
I don't think that will work if configured with --without-libffi.
I'm goin
I reopened this PR to do some cleanup and to address a use case presented by
Joost in comment #7 of the subject PR.
The fundamental problem: if the variable containing the unit number in an
INQUIRE statement is of type KIND greater than 4 and the value is outside the
range of a KIND=4 we canno
On Sun, Jan 18, 2015 at 05:28:39PM -0600, Segher Boessenkool wrote:
> On Sat, Jan 17, 2015 at 01:18:44PM -0500, Hans-Peter Nilsson wrote:
> > The current cc-first order happened more of an accidental
> > opinion than an architectural decision as I vaguely recall, when
> > asking. We also have the
On Mon, 8 Dec 2014, Segher Boessenkool wrote:
> A lot of old user code clobbers the carry bit without telling the compiler
> about it. This used to just work, because the compiler never used the bit
> outside of a single RTL instruction. But that will change. Let's clobber
> the carry bit in ev
Hi Gerald,
how about the following variation (which I have not committed yet)?
The wording is good but the patch places the comment into gcc-ar section
which is wrong. Perhaps make a separate section for driver like this?
-Y
Index: htdocs/gcc-5/changes.html
=
33 matches
Mail list logo
