https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71572
Andrew Pinski changed:
What|Removed |Added
Component|c |inline-asm
--- Comment #1 from Andrew
On Fri, Jun 17, 2016 at 7:29 AM, Martin Liška wrote:
> Hello.
>
> After we've recently applied various changes (fixes) to predict.c, SPEC2006
> shows that PRED_LOOP_EXIT value should be amended.
This caused a 1% decrease of performance on coremarks on
aarch64-linux-gnu on
with: ../gcc-source-trunk/configure --enable-languages=c,c++,lto
--prefix=/usr/local/gcc-trunk --disable-bootstrap
Thread model: posix
gcc version 7.0.0 20160617 (experimental) [trunk revision 237557] (GCC)
$
$ g++-6.1 -c small.cpp
small.cpp:1:36: error: too many initializers for ‘’
struct { int a; } s1
-source-trunk/configure --enable-languages=c,c++,lto
--prefix=/usr/local/gcc-trunk --disable-bootstrap
Thread model: posix
gcc version 7.0.0 20160617 (experimental) [trunk revision 237557] (GCC)
$
$ g++-6.1 -c small.cpp
$
$ g++-trunk -c small.cpp
small.cpp: In function ‘void foo()’:
small.cpp:10:26
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71575
--- Comment #1 from Aric Belsito ---
Forgot this in OP:
$ gcc -v
Using built-in specs.
COLLECT_GCC=/usr/x86_64-gentoo-linux-musl/gcc-bin/6.1.0/gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-gentoo-linux-musl/6.1.0/lto-wrapper
Target:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71575
Bug ID: 71575
Summary: internal compiler error: in copy_cond_phi_nodes, at
graphite-isl-ast-to-gimple.c:2500
Product: gcc
Version: 6.1.0
Status: UNCONFIRMED
-trunk/configure --enable-languages=c,c++,lto
--prefix=/usr/local/gcc-trunk --disable-bootstrap
Thread model: posix
gcc version 7.0.0 20160617 (experimental) [trunk revision 237557] (GCC)
$
$ gcc-trunk -c small.c
small.c:2:1: internal compiler error: in default_conversion, at
c/c-typeck.c:2118
int fn2
with: ../gcc-source-trunk/configure --enable-languages=c,c++,lto
--prefix=/usr/local/gcc-trunk --disable-bootstrap
Thread model: posix
gcc version 7.0.0 20160617 (experimental) [trunk revision 237557] (GCC)
$:
$: gcc-trunk small.c
small.c: In function ‘f2’:
small.c:4:3: internal compiler error
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71571
Hans-Peter Nilsson changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71571
Hans-Peter Nilsson changed:
What|Removed |Added
CC||hp at gcc dot gnu.org
++,lto
--prefix=/usr/local/gcc-trunk --disable-bootstrap
Thread model: posix
gcc version 7.0.0 20160617 (experimental) [trunk revision 237557] (GCC)
$
$ clang-3.8 -c small.c
$
$ gcc-trunk -c small.c
small.c: In function ‘fn1’:
small.c:7:3: internal compiler error: in force_constant_size
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71338
--- Comment #2 from dj at gcc dot gnu.org ---
Author: dj
Date: Fri Jun 17 22:24:17 2016
New Revision: 237566
URL: https://gcc.gnu.org/viewcvs?rev=237566=gcc=rev
Log:
PR target/71338
* config/rl78/rl78-expand.c (umulqihi3): Enable for G10.
*
Reverts https://gcc.gnu.org/ml/gcc-patches/2014-08/msg01538.html - G10
supports MULU but not other multiplication methods. Committed.
PR target/71338
* config/rl78/rl78-expand.c (umulqihi3): Enable for G10.
* config/rl78/rl78-virtual.c (umulhi3_shift_virt): Likewise.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71435
--- Comment #12 from Eric Botcazou ---
> The tentative fix restored bootstrap on sparc-linux. Test results look
> OK-ish.
Thanks, I'll post it tomorrow morning.
This patch adds explicit testing of lexing a source file,
generalizing this (and the test of ordinary line maps) over
a 2-dimensional test matrix covering:
(1) line_table->default_range_bits: some frontends use a non-zero value
and others use zero
(2) the fallback modes within line-map.c:
Hi,
Please find the patch for introducing vulcan as a cpu name for the
AArch64 port of GCC.
Broadcom's vulcan is an armv8.1-a aarch64 server processor.
Since vulcan is the first armv8.1-a processor to be introduced in
aarch64-cores.def,
I have created a new section in the file for the armv8.1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71435
--- Comment #11 from Mikael Pettersson ---
(In reply to Mikael Pettersson from comment #10)
> (In reply to Eric Botcazou from comment #9)
> > > Created attachment 38699 [details]
> > > Tentative fix.
> >
> > It successfully passed a full
On 2016-06-15 17:15, Martin Sebor wrote:
There has been quite a bit of discussion among the committee on
this subject lately (the last part is the subject of DR #451,
though it's discussed in the context of uninitialized objects
with indeterminate values).
Are there notes from these
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71559
--- Comment #11 from joseph at codesourcery dot com ---
On Fri, 17 Jun 2016, jakub at gcc dot gnu.org wrote:
> The patch is completely untested though (and wonder if we have testcases for
> not raising exceptions when isgreater etc. arguments
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71571
David B. Robins changed:
What|Removed |Added
Target||crisv32-axis-linux-gnu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71571
--- Comment #2 from David B. Robins ---
Created attachment 38721
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=38721=edit
Larger repro - crashes reliably - requires additional -O2 -fno-inline
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71571
--- Comment #1 from David B. Robins ---
Created attachment 38720
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=38720=edit
Small repro - emits branch (ba) without delay-slot instruction
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71571
Bug ID: 71571
Summary: [CRIS] Multiple inheritance non-virtual PIC thunk
causes crash
Product: gcc
Version: 4.3.1
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71545
Jonathan Wakely changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
We can use rich_location and the new diagnostic_show_locus to print
both locations when complaining about a bogus string concatenation
in the C++ FE, giving e.g.:
test.C:3:24: error: unsupported non-standard concatenation of string literals
const void *s = u8"a" u"b";
~
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71545
--- Comment #4 from Jonathan Wakely ---
Author: redi
Date: Fri Jun 17 18:53:46 2016
New Revision: 237561
URL: https://gcc.gnu.org/viewcvs?rev=237561=gcc=rev
Log:
libstdc++/71545 fix debug checks in binary search algorithms
PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71559
--- Comment #10 from H.J. Lu ---
This is related to PR 37158?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71545
--- Comment #3 from Jonathan Wakely ---
Author: redi
Date: Fri Jun 17 18:28:34 2016
New Revision: 237560
URL: https://gcc.gnu.org/viewcvs?rev=237560=gcc=rev
Log:
libstdc++/71545 fix debug checks in binary search algorithms
PR
PR libstdc++/71545
* include/bits/stl_algobase.h (lower_bound, lexicographical_compare):
Remove irreflexive checks.
* include/bits/stl_algo.h (lower_bound, upper_bound, equal_range,
binary_search): Likewise.
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71548
Martin Sebor changed:
What|Removed |Added
Keywords||ice-on-invalid-code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71559
--- Comment #9 from Jakub Jelinek ---
If I compile the above testcase with -O2 -mavx -ftrapping-math, then it
generates vucomiss in each case, which seems wrong to me (because for
gt/ge/lt/le it should raise exceptions, so IMHO should use
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71559
Jakub Jelinek changed:
What|Removed |Added
CC||hjl.tools at gmail dot com,
: x86_64-pc-linux-gnu
Configured with: ../gcc-source-trunk/configure --enable-languages=c,c++,lto
--prefix=/usr/local/gcc-trunk --disable-bootstrap
Thread model: posix
gcc version 7.0.0 20160617 (experimental) [trunk revision 237557] (GCC)
$
$ g++-trunk -c small.cpp
small.cpp: In function ‘void foo
OK.
Jason
On Wed, Jun 15, 2016 at 5:15 AM, Paolo Carlini wrote:
> + /* Likewise for the constexpr specifier, in case t is a specialization
> + and we are emitting an error about an incompatible redeclaration. */
It doesn't need to be in an error about a redeclaration; in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71569
Martin Sebor changed:
What|Removed |Added
Keywords||ice-on-invalid-code
OK.
Jason
On Wednesday 01 June 2016 10:00:52 Ramana Radhakrishnan wrote:
> Please fix up the macros, post back and redo the test. Otherwise this
> is ok from a quick read.
What about the updated patch in attachment? As for the original patch, I've
checked that code generation does not change for a number
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71143
--- Comment #7 from Vidya Praveen ---
Author: jason
Date: Fri Jun 17 16:35:33 2016
New Revision: 237558
URL: https://gcc.gnu.org/viewcvs?rev=237558=gcc=rev
Log:
PR c++/71209 - wrong error with dependent base
* typeck.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71550
Jeffrey A. Law changed:
What|Removed |Added
CC||law at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71560
Martin Sebor changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71569
Bug ID: 71569
Summary: [5/6] Crash: External definition of template member
from template struct
Product: gcc
Version: 5.1.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71143
Markus Trippelsdorf changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
On 06/17/2016 07:07 AM, Jakub Sejdak wrote:
So at least in the immediate term let's get you write privileges so you can
commit approved changes and on the path towards maintaining the Phoenix-RTOS
configurations.
Do I have to apply for this permission somewhere? Provided page states
only, that
On 06/17/2016 07:14 AM, Martin Liška wrote:
Hi.
Following simple patch fixes a newly introduced memory leak.
Patch survives regression tests and bootstraps on x86_64-linux.
Ready from trunk?
Thanks,
Martin
0001-Fix-memory-leak-in-tree-ssa-reassoc.c.patch
From
On 06/17/2016 08:33 AM, Ilya Enkovich wrote:
Hmm, there seems to be a level of indirection I'm missing here. We're
smuggling LOOP_VINFO_ORIG_LOOP_INFO around in loop->aux. Ewww. I thought
the whole point of LOOP_VINFO_ORIG_LOOP_INFO was to smuggle the VINFO from
the original loop to the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71209
--- Comment #2 from Jason Merrill ---
Author: jason
Date: Fri Jun 17 16:35:33 2016
New Revision: 237558
URL: https://gcc.gnu.org/viewcvs?rev=237558=gcc=rev
Log:
PR c++/71209 - wrong error with dependent base
* typeck.c
Now that we have stopped treating *this as a dependent scope, we need
to avoid giving errors for not finding things when we have dependent
bases.
Tested x86_64-pc-linux-gnu, applying to trunk.
commit d553bc7ff104a8d973c3f48c005457038422db26
Author: Jason Merrill
Date: Fri Jun
On 06/16/2016 02:32 AM, Aldy Hernandez wrote:
Hi folks!
I've been working on a plugin to warn on unbounded uses of alloca() to
help find questionable uses in glibc and other libraries. It occurred
to me that the broader community could benefit from it, as it has found
quite a few interesting
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71143
Jason Merrill changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
On 06/17/2016 08:29 AM, Michael Matz wrote:
Hi,
On Fri, 17 Jun 2016, Bernd Schmidt wrote:
On 06/17/2016 04:03 PM, Michael Matz wrote:
But does this really improve something? Essentially you're replacing
0xc9 0xc3
(the end of a function containing "leave;ret") with
0xe9
where
On Fri, Jun 17, 2016 at 4:37 PM, Jeff Law wrote:
> On 06/17/2016 08:48 AM, Bin.Cheng wrote:
> + /* FORNOW: Currently alias checks are not inherited for epilogues.
> + Don't try to vectorize epilogue because it will require
> + additional alias
On 06/17/2016 04:06 AM, Bernd Schmidt wrote:
This is another step to flesh out -mmitigate-rop for i386 a little more.
The basic idea was (I think) Richard Henderson's: if we could arrange to
have every return preceded by a leave instruction, it would make it
harder to construct an attack since
On 06/17/2016 08:16 AM, Ilya Enkovich wrote:
I do think you've got a legitimate question though. Ilya, can you give any
insights here based on your KNL and Haswell testing or data/insights from
the LLVM and/or ICC teams?
I have no information about LLVM. As I said in other thread ICC uses
On 06/17/2016 08:48 AM, Bin.Cheng wrote:
+ /* FORNOW: Currently alias checks are not inherited for epilogues.
+ Don't try to vectorize epilogue because it will require
+ additional alias checks. */
Are the alias checks here redundant with the ones done for the original
loop? If so
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71559
--- Comment #7 from Jakub Jelinek ---
I've created the table just by walking through the 'D' handling.
That said, looking e.g. at
https://people.eecs.berkeley.edu/~wkahan/ieee754status/IEEE754.PDF
for the C comparisons (EQ, NE, LT, LE, GT, GE)
Hi all,
I'm working on a tree-ssa pass to implement PR 22141, a pass that merges
adjacent stores.
I've gotten to the point where I can identify the adjacent accesses, merge them
into a single value
and am now working on emitting the new statements but, as I don't have a lot of
experience with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71545
--- Comment #2 from Jonathan Wakely ---
The irreflexive assertion is incorrect for lexicographical compare too:
#include
struct X { };
bool operator<(X, int) { return true; }
bool operator<(int, X) { return false; }
// Not a strict weak
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71559
--- Comment #6 from Carlos Tripiana Montes ---
Hope you guys can do that and fix this problem soon. It would much appreciated
as we are (at Barcelona Supercomputing Center, Spain) doing research on KNL and
we need the fastest/most robust code we
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71568
Bug ID: 71568
Summary: Inexplicable error: "X is inaccessible within this
context" for a public member
Product: gcc
Version: 6.1.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71559
Ilya Enkovich changed:
What|Removed |Added
CC||ienkovich at gcc dot gnu.org
---
On 04/04/14 20:48, dw wrote:
> I do not have write permissions to check this patch in.
We must fix that.
Andrew.
2016-06-17 17:48 GMT+03:00 Bin.Cheng :
> On Fri, Jun 17, 2016 at 3:33 PM, Ilya Enkovich wrote:
>> 2016-06-16 9:00 GMT+03:00 Jeff Law :
>>> On 05/19/2016 01:39 PM, Ilya Enkovich wrote:
Hi,
This patch introduces
On 17 June 2016 at 16:44, James Greenhalgh wrote:
> On Fri, Jun 17, 2016 at 04:25:31PM +0200, Christophe Lyon wrote:
>> On 10 June 2016 at 14:29, James Greenhalgh wrote:
>> >
>> > Hi,
>> >
>> > My autotester picked up some issues with the
On Fri, Jun 17, 2016 at 3:33 PM, Ilya Enkovich wrote:
> 2016-06-16 9:00 GMT+03:00 Jeff Law :
>> On 05/19/2016 01:39 PM, Ilya Enkovich wrote:
>>>
>>> Hi,
>>>
>>> This patch introduces changes required to run vectorizer on loop epilogue.
>>> This also
On Fri, Jun 17, 2016 at 04:25:31PM +0200, Christophe Lyon wrote:
> On 10 June 2016 at 14:29, James Greenhalgh wrote:
> >
> > Hi,
> >
> > My autotester picked up some issues with the vcvt{ds}_n_* intrinsics
> > added in r237200.
> >
> Hi,
>
> What tests does your
On Wed, Jun 15, 2016 at 08:12:15PM -0700, Cesar Philippidis wrote:
> The second set of changes involves teaching the gimplifier to error when
> it detects a function call to an non-acc routines inside an OpenACC
> offloaded region. Actually, I relaxed non-acc routines by excluding
> calls to
Ping.
https://gcc.gnu.org/ml/gcc-patches/2016-06/msg00821.html
Thanks,
Kyrill
On 10/06/16 15:55, Kyrill Tkachov wrote:
Hi all,
This function just ICEs and isn't actually called from anywhere.
It was introduced back in 2000 as part of a large merge introducing Thumb
support
and was aborting
On Thu, Jun 16, 2016 at 08:22:29PM -0700, Cesar Philippidis wrote:
> --- a/gcc/fortran/openmp.c
> +++ b/gcc/fortran/openmp.c
> @@ -677,7 +677,6 @@ gfc_match_omp_clauses (gfc_omp_clauses **cp, uint64_t
> mask,
> && gfc_match ("async") == MATCH_YES)
> {
> c->async
On 06/17/2016 04:29 PM, Michael Matz wrote:
On Fri, 17 Jun 2016, Bernd Schmidt wrote:
On 06/17/2016 04:03 PM, Michael Matz wrote:
But does this really improve something? Essentially you're replacing
0xc9 0xc3
(the end of a function containing "leave;ret") with
0xe9
where the four
2016-06-16 9:00 GMT+03:00 Jeff Law :
> On 05/19/2016 01:39 PM, Ilya Enkovich wrote:
>>
>> Hi,
>>
>> This patch introduces changes required to run vectorizer on loop epilogue.
>> This also enables epilogue vectorization using a vector of smaller size.
>>
>> Thanks,
>> Ilya
>> --
>>
Hi,
On Fri, 17 Jun 2016, Bernd Schmidt wrote:
> On 06/17/2016 04:03 PM, Michael Matz wrote:
> > But does this really improve something? Essentially you're replacing
> >
> >0xc9 0xc3
> >
> > (the end of a function containing "leave;ret") with
> >
> >0xe9
> >
> > where the four
Hello.
After we've recently applied various changes (fixes) to predict.c, SPEC2006
shows that PRED_LOOP_EXIT value should be amended.
Survives regression tests & bootstrap on x86_64-linux.
Pre-approved by Honza, installed as r237556.
Thanks,
Martin
>From 849c2e064bcadc269f82656d15722f28d1b1fe73
Hi Christophe,
On 17/06/16 11:47, Christophe Lyon wrote:
Hi,
As discussed some time ago with Kyrylo (on IRC IIRC), the attached
patch makes sure that arm_neon_fp16_ok and arm_neonv2_ok effective
targets imply that arm_neon_ok passes, and use the corresponding
flags.
Without this patch, the 3
On 10 June 2016 at 14:29, James Greenhalgh wrote:
>
> Hi,
>
> My autotester picked up some issues with the vcvt{ds}_n_* intrinsics
> added in r237200.
>
Hi,
What tests does your autotester perform? I haven't noticed these
problems when running the GCC testsuite on the
On 14 June 2016 at 18:31, Prathamesh Kulkarni
wrote:
> On 13 June 2016 at 16:13, Jan Hubicka wrote:
>>> diff --git a/gcc/cgraph.h b/gcc/cgraph.h
>>> index ecafe63..41ac408 100644
>>> --- a/gcc/cgraph.h
>>> +++ b/gcc/cgraph.h
>>> @@ -1874,6 +1874,9
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71567
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
Hello,
An initial patch has been integrated into gnu-config to translate triplets like
e500v2-*- into powerpc-*-spe.
The spe extension to the os is expected for targets such as e500v[12]-*-linux
(translated as powerpc-*-linux-gnuspe) or eabi targets.
This patch integrates the patch of
On 06/17/2016 04:03 PM, Michael Matz wrote:
But does this really improve something? Essentially you're replacing
0xc9 0xc3
(the end of a function containing "leave;ret") with
0xe9
where the four random bytes are different for each rewritten function
return (but correlated as they
2016-06-16 8:22 GMT+03:00 Jeff Law :
> On 06/15/2016 05:03 AM, Richard Biener wrote:
>>
>> On Thu, May 19, 2016 at 9:39 PM, Ilya Enkovich
>> wrote:
>>>
>>> Hi,
>>>
>>> This patch introduces changes required to run vectorizer on loop
>>> epilogue. This also
On Fri, Jun 17, 2016 at 10:40:40AM +0200, Tobias Burnus wrote:
> Cesar Philippidis wrote:
> > On 06/16/2016 08:30 PM, Cesar Philippidis wrote:
> > > This patch introduces a match_acc function to the fortran FE. It's
> > > almost identical to match_omp, but it passes openacc = true to
> > >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71508
--- Comment #2 from Paul Olaru
---
Created attachment 38716
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=38716=edit
Preprocessed source (gzipped)
The uncompressed file is barely above 1MB.
On Thu, Jun 16, 2016 at 09:05:40PM +0200, Jakub Jelinek wrote:
> Fixed thusly, bootstrapped/regtested on x86_64-linux and i686-linux, and
> tested with x86_64-intelmicemul-linux offloading on x86_64-linux, committed
> to trunk.
And the following testcase shows similar issues in the array section
Hi,
On Fri, 17 Jun 2016, Bernd Schmidt wrote:
> This is another step to flesh out -mmitigate-rop for i386 a little more.
> The basic idea was (I think) Richard Henderson's: if we could arrange to
> have every return preceded by a leave instruction, it would make it
> harder to construct an
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71354
--- Comment #3 from amker at gcc dot gnu.org ---
Author: amker
Date: Fri Jun 17 13:55:06 2016
New Revision: 237555
URL: https://gcc.gnu.org/viewcvs?rev=237555=gcc=rev
Log:
PR tree-optimization/71354
* gcc.dg/vect/vect-23.c: Use
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71567
Bug ID: 71567
Summary: Incorrect loop optimization
Product: gcc
Version: 4.8.5
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71544
--- Comment #6 from fortranbug at gmail dot com ---
Thank you for the suggested workaround. This can certainly be helpful in the
short term. However, we would not want to rely on tuning compiler optimization
switches in the future to ensure
Hi.
Following simple patch fixes a newly introduced memory leak.
Patch survives regression tests and bootstraps on x86_64-linux.
Ready from trunk?
Thanks,
Martin
>From a2e6be16d7079b744db4d383b8317226ab53ff58 Mon Sep 17 00:00:00 2001
From: marxin
Date: Fri, 17 Jun 2016 12:26:58
> So at least in the immediate term let's get you write privileges so you can
> commit approved changes and on the path towards maintaining the Phoenix-RTOS
> configurations.
Do I have to apply for this permission somewhere? Provided page states
only, that it has to be granted by an existing
On 16 June 2016 at 14:56, Jan Hubicka wrote:
> Hi,
> tree_estimate_loop_size contains one extra else that prevents it from
> determining
> that the induction variable comparsion is going to be eliminated in both the
> peeled
> copies as well as the last copy. This patch fixes
Senthil Kumar Selvaraj schrieb:
Hi,
This patch fixes PR 71151 by eliminating the
TARGET_ASM_FUNCTION_RODATA_SECTION hook and setting
JUMP_TABLES_IN_TEXT_SECTION to 1.
As described in the bugzilla entry, this hook assumed it will get
called only for jumptable rodata for functions.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59861
milasudril at gmail dot com changed:
What|Removed |Added
Severity|minor |enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71541
--- Comment #6 from Hans Philipp Annen ---
> -Wl,--whole-archive -lpthread -Wl,--no-whole-archive
This did help.
Without it, the destructor of condition_variable just jumps to nowhere:
> Dump of assembler code for function
Hi,
one more I missed. Tested x86_64-linux. Should be obvious too...
Thanks,
Paolo.
PS: I still have pending:
https://gcc.gnu.org/ml/gcc-patches/2016-06/msg01116.html
//
/cp
2016-06-17 Paolo Carlini
* decl.c (grokfndecl): Change pair
On 06/17/2016 12:37 PM, Jakub Jelinek wrote:
Do you really need to require frame pointer for this?
I mean, couldn't you instead use what you do if a function needs frame
pointer and otherwise just replace the original ret with
pushq %rbp
movq%rsp, %rbp
jmp
Hi,
As discussed some time ago with Kyrylo (on IRC IIRC), the attached
patch makes sure that arm_neon_fp16_ok and arm_neonv2_ok effective
targets imply that arm_neon_ok passes, and use the corresponding
flags.
Without this patch, the 3 effective targets have different, possibly
inconsistent
2016-06-16 8:06 GMT+03:00 Jeff Law :
> On 05/20/2016 05:40 AM, Ilya Enkovich wrote:
>>
>> 2016-05-20 14:17 GMT+03:00 Richard Biener :
>>>
>>> On Fri, May 20, 2016 at 11:50 AM, Ilya Enkovich
>>> wrote:
2016-05-20 12:26
On Fri, Jun 17, 2016 at 12:06:48PM +0200, Bernd Schmidt wrote:
> This is another step to flesh out -mmitigate-rop for i386 a little more. The
> basic idea was (I think) Richard Henderson's: if we could arrange to have
> every return preceded by a leave instruction, it would make it harder to
>
This is another step to flesh out -mmitigate-rop for i386 a little more.
The basic idea was (I think) Richard Henderson's: if we could arrange to
have every return preceded by a leave instruction, it would make it
harder to construct an attack since it takes away a certain amount of
control
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71562
--- Comment #2 from Peter VARGA ---
I disagree 100% with your comment!
I am definitely NOT a genius and I needed 5 minutes to find out where the hard
coded size is set.
Look at the GNU Glibc - you can crash an existing
1 - 100 of 124 matches
Mail list logo