Hi,
as was figured out in PR LTO + ASan raises false initialization order
fiasco alarm due to in LTO case main_input_filename doesn't match module
name passed to __asan_before_dynamic_init.
Following Jakub's suggestion I used TRANSLATION_UNIT_DECL for
corresponding globals to overcome this
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79125
Arseny Solokha changed:
What|Removed |Added
Keywords||ice-on-valid-code
--- Comment #1 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79125
Bug ID: 79125
Summary: [7 Regression] ICE in rtl_verify_bb_insns, at
cfgrtl.c:2661 (error: flow control insn inside a basic
block)
Product: gcc
Version: 7.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78875
Thomas Schwinge changed:
What|Removed |Added
CC||tschwinge at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=29838
--- Comment #12 from Thomas Schwinge ---
See also PR78875.
On 01/17/2017 08:16 PM, Martin Sebor wrote:
On 01/17/2017 12:38 AM, Jakub Jelinek wrote:
On Mon, Jan 16, 2017 at 05:06:40PM -0700, Martin Sebor wrote:
The test case submitted in bug 79095 - [7 regression] spurious
stringop-overflow warning shows that GCC optimizes some loops
into calls to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72488
--- Comment #9 from Jeffrey A. Law ---
So, just to record some thoughts.
There's about a half-dozen patches, mostly from the August timeframe that will
make this bug go latent. The general theme across them is they change the
order in which we
Committed. Thanks!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79124
Bug ID: 79124
Summary: Internal compiler error under certain cases where
__attribute__((target("avx2"))) presents
Product: gcc
Version: 5.4.1
Status: UNCONFIRMED
On Mon, Jan 16, 2017 at 7:21 AM, Rainer Orth
wrote:
>
> I'm getting further on Solaris now, but the build still fails:
I committed this patch to fix the remaining build problems on Solaris.
Bootstrapped and ran some of the Go tests on i386-sun-solaris11 and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79122
--- Comment #2 from Ian Lance Taylor ---
Note that the race detector doesn't work at all with gccgo. So while this is a
pretty bad error message, the only fix for this bug is going to be to produce a
better error message.
On 01/17/2017 12:38 AM, Jakub Jelinek wrote:
On Mon, Jan 16, 2017 at 05:06:40PM -0700, Martin Sebor wrote:
The test case submitted in bug 79095 - [7 regression] spurious
stringop-overflow warning shows that GCC optimizes some loops
into calls to memset with size arguments in excess of the
On 01/17/2017 10:57 AM, Jeff Law wrote:
On 01/17/2017 09:12 AM, Martin Sebor wrote:
On 01/17/2017 08:26 AM, Jeff Law wrote:
On 01/16/2017 05:06 PM, Martin Sebor wrote:
The test case submitted in bug 79095 - [7 regression] spurious
stringop-overflow warning shows that GCC optimizes some loops
This patch adds support for adding built-in functions for the ISA 3.0 vector
byte reverse instructions (XXBR{Q,D,W,H}).
The vec_revb built-in function follows the specifications in the OpenPOWER ABI
for Linux Supplement Power Architecture 64-Bit ELF V2 ABI and reverses the
bytes in each vector
This patch adds test gcc.dg/strncmp-2.c for builtin expansion of
strncmp and strcmp. This tests a couple more things such as differences
that occur after the zero byte, and something that glibc does which is
to call strncmp with SIZE_MAX for the length which looks for overflow
issues.
I've
On Tue, Jan 17, 2017 at 07:00:36PM -0600, Segher Boessenkool wrote:
> On Tue, Jan 17, 2017 at 07:39:05PM -0500, Michael Meissner wrote:
> > It turns out the testcase I submitted for pr79004 failed, since I had the
> > wrong
> > syntax for \m and \M (you need to use {\m...\M} not "\m...\M".
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79123
Bug ID: 79123
Summary: incorrect -Walloca-larger-than: alloca may be too
large due to conversion from long int to long unsigned
int
Product: gcc
Version: 7.0
On Tue, Jan 17, 2017 at 07:39:05PM -0500, Michael Meissner wrote:
> It turns out the testcase I submitted for pr79004 failed, since I had the
> wrong
> syntax for \m and \M (you need to use {\m...\M} not "\m...\M".
You can use quotes, but then it is "\\m...\\M", like with all backslashes
in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79004
Michael Meissner changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
On Wed, Jan 11, 2017 at 04:39:19PM -0600, Segher Boessenkool wrote:
> On Mon, Jan 09, 2017 at 07:32:27PM -0500, Michael Meissner wrote:
> > This patch fixes PR target/79004 by eliminating the optimization of avoiding
> > direct move if we are converting an 8/16-bit integer value from memory to
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79004
--- Comment #7 from Michael Meissner ---
Author: meissner
Date: Wed Jan 18 00:35:29 2017
New Revision: 244561
URL: https://gcc.gnu.org/viewcvs?rev=244561=gcc=rev
Log:
2017-01-17 Michael Meissner
PR
On Tue, Jan 10, 2017 at 03:40:00PM +0100, Martin Liška wrote:
> On 01/10/2017 02:56 PM, Richard Biener wrote:
> >On Mon, Jan 9, 2017 at 4:05 PM, Martin Liška wrote:
> >>Second part of the patch does sorting of final congruence classes, it's
> >>groups
> >>and items included in
On 01/17/2017 02:21 AM, Richard Biener wrote:
So I guess my question is how do you ensure that even though cgraph hasn't
looked at code that we're appropriately conservative with how the file is
processed? Particularly if there's other code in the source file that is
expected to interact with
On 01/17/2017 05:41 AM, Moore, Catherine wrote:
>
>
>> ...
>> Having thought further I agree we can safely ignore DSP indexed load
>> and micromips LWXS on
>> the basis that DSP code will not run on a MIPS64 processor anyway (at
>> least none that I
>> know of) so the issue cannot occur and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79112
--- Comment #5 from Kazumoto Kojima ---
It seems that the error message says all. TIOCGWINSZ is defined as
#define TIOCGWINSZ0x80087468 /* _IOR('t', 104, struct winsize) */
in the SH kernel header asm/ioctls.h. Perhaps you could
On 1/17/17 3:27 PM, Jonathan Wakely wrote:
On 17/01/17 14:55 -0800, Josh Conner via libstdc++ wrote:
On 1/17/17 2:35 PM, Jonathan Wakely wrote:
On 17/01/17 13:15 -0800, Josh Conner via libstdc++ wrote:
This patch adds fuchsia support to libstdc++. OK for trunk?
Is fuchsia only supported as
kugan wrote:
> Wilco Dijkstra wrote:
> > + /* Slightly disparage left shift by 1 at so we prefer adddi3. */
> > + if (code == ASHIFT && XEXP (x, 1) == CONST1_RTX (SImode))
> Your ChangeLog says decrease cost for ashldi3 by 1 but looks like it is
> done only for SImode. Am I missing
On 17/01/17 14:55 -0800, Josh Conner via libstdc++ wrote:
On 1/17/17 2:35 PM, Jonathan Wakely wrote:
On 17/01/17 13:15 -0800, Josh Conner via libstdc++ wrote:
This patch adds fuchsia support to libstdc++. OK for trunk?
Is fuchsia only supported as a cross-compiler target, not native?
For the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79122
--- Comment #1 from Alan ---
Reported as:
https://github.com/golang/go/issues/18696
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79122
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79122
Bug ID: 79122
Summary: go test -race reports import cycles with gccgo
Product: gcc
Version: 6.3.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
On 1/17/17 2:35 PM, Jonathan Wakely wrote:
On 17/01/17 13:15 -0800, Josh Conner via libstdc++ wrote:
This patch adds fuchsia support to libstdc++. OK for trunk?
Is fuchsia only supported as a cross-compiler target, not native?
For the moment. I have a patch that adds fuchsia support to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77445
seurer at gcc dot gnu.org changed:
What|Removed |Added
CC||seurer at gcc dot gnu.org
Snapshot gcc-5-20170117 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/5-20170117/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 5 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-5
On 17/01/17 13:15 -0800, Josh Conner via libstdc++ wrote:
This patch adds fuchsia support to libstdc++. OK for trunk?
Is fuchsia only supported as a cross-compiler target, not native?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78875
--- Comment #2 from Segher Boessenkool ---
Author: segher
Date: Tue Jan 17 22:02:42 2017
New Revision: 244556
URL: https://gcc.gnu.org/viewcvs?rev=244556=gcc=rev
Log:
-mstack-protector-guard and friends (PR78875)
Currently, on PowerPC, code
Hi Vladimir,
On 17 January 2017 at 17:14, Vladimir Makarov wrote:
> The following patch fixes
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79058
>
> The patch was successfully bootstrapped and tested on x86-64.
>
> Committed as rev. 244535.
>
>
The new testcase fails to
On Tue, Jan 17, 2017 at 12:43 PM, Segher Boessenkool
wrote:
> Currently, on PowerPC, code compiled with -fstack-protector will load
> the canary from -0x7010(13) (for -m64) or from -0x7008(2) (for -m32)
> if GCC was compiled against GNU libc 2.4 or newer or some other
Gerald -
Attached is my recommended patch for changes to the web docs describing Fuchsia
support. Please let
me know if there's anything else I can do.
Thanks!
- Josh
On 12/11/16 7:24 AM, Gerald Pfeifer wrote:
On Thu, 8 Dec 2016, Josh Conner wrote:
This patch adds support to gcc for the
Applied.
--
Eric BotcazouIndex: gcc-7/changes.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-7/changes.html,v
retrieving revision 1.38
diff -r1.38 changes.html
57c57,61
<
---
> Ada
>
> On mainstream native platforms, Ada
Hi Wilco,
On 18/01/17 06:23, Wilco Dijkstra wrote:
ChangeLog:
2017-01-17 Wilco Dijkstra
* config/arm/arm.md (ashldi3): Remove shift by 1 expansion.
(arm_ashldi3_1bit): Remove pattern.
(ashrdi3): Remove shift by 1 expansion.
On Tue, Jan 17, 2017 at 12:48 PM, Karsten Merker wrote:
> On Mon, Jan 16, 2017 at 09:37:15PM -0800, Palmer Dabbelt wrote:
>> On Sat, 14 Jan 2017 02:05:27 PST (-0800), mer...@debian.org wrote:
>> > Palmer Dabbelt wrote:
>> >
>> >> diff --git a/gcc/config/riscv/linux.h
This patch adds fuchsia support to libstdc++. OK for trunk?
Thanks -
Josh
2017-01-17 Joshua Conner
* crossconfig.m4: Add fuchsia OS.
* configure: Regenerate.
Index: configure
===
---
On Tue, 2017-01-17 at 10:45 +0100, Christophe Lyon wrote:
> On 16 January 2017 at 19:50, David Malcolm
> wrote:
> > On Mon, 2017-01-16 at 13:31 +0100, Rainer Orth wrote:
> > > Hi Christophe,
> > >
> > > > > Successfully bootstrapped on x86_64-pc-linux-gnu;
> > > > > adds 34
On Tue, 2017-01-17 at 10:28 +0100, Richard Biener wrote:
> On Mon, Jan 16, 2017 at 10:42 PM, Jeff Law wrote:
> > On 01/09/2017 07:38 PM, David Malcolm wrote:
> > >
> > > gcc/ChangeLog:
> > > * passes.c: Include "insn-addr.h".
> > > (should_skip_pass_p): Add
On Tue, Jan 17, 2017 at 05:43:54PM +, Segher Boessenkool wrote:
> Currently, on PowerPC, code compiled with -fstack-protector will load
> the canary from -0x7010(13) (for -m64) or from -0x7008(2) (for -m32)
> if GCC was compiled against GNU libc 2.4 or newer or some other libc
> that supports
On 01/17/2017 03:41 PM, Steve Silva wrote:
Hi Nathan,
Thanks for your advice. I retooled the addhi3 sequence to look like this:
The md.texi file seems to have exactly the example you need:
Here for example, is how the 68000 halfword-add
instruction is defined:
@smallexample
(define_insn
Hi Nathan,
Thanks for your advice. I retooled the addhi3 sequence to look like this:
(define_expand "addhi3"
[(set (match_operand:HI 0 "snap_mem_or_reg""+a,m")
(plus:HI (match_operand:HI 1 "snap_mem_or_reg" "%0,0")
(match_operand:HI 2 "general_operand" "aim,aim")))]
""
""
)
Hi!
I've backported a couple of patches to gcc-6-branch after
bootstrapping/regtesting them on x86_64-linux and i686-linux.
Jakub
2017-01-17 Jakub Jelinek
Backported from mainline
2016-12-21 Jakub Jelinek
PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78839
--- Comment #14 from Jakub Jelinek ---
Author: jakub
Date: Tue Jan 17 20:34:58 2017
New Revision: 244555
URL: https://gcc.gnu.org/viewcvs?rev=244555=gcc=rev
Log:
PR debug/78839
* dwarf2out.c (field_byte_offset): Restore the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69600
--- Comment #6 from sshannin at gmail dot com ---
Thanks for the update : )
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78341
--- Comment #6 from Jakub Jelinek ---
Author: jakub
Date: Tue Jan 17 20:34:17 2017
New Revision: 244554
URL: https://gcc.gnu.org/viewcvs?rev=244554=gcc=rev
Log:
Backported from mainline
2017-01-11 Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50199
--- Comment #30 from Jakub Jelinek ---
Author: jakub
Date: Tue Jan 17 20:33:16 2017
New Revision: 244553
URL: https://gcc.gnu.org/viewcvs?rev=244553=gcc=rev
Log:
Backported from mainline
2017-01-11 Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78949
--- Comment #8 from Jakub Jelinek ---
Author: jakub
Date: Tue Jan 17 20:32:27 2017
New Revision: 244552
URL: https://gcc.gnu.org/viewcvs?rev=244552=gcc=rev
Log:
Backported from mainline
2017-01-04 Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78693
--- Comment #7 from Jakub Jelinek ---
Author: jakub
Date: Tue Jan 17 20:31:40 2017
New Revision: 244551
URL: https://gcc.gnu.org/viewcvs?rev=244551=gcc=rev
Log:
Backported from mainline
2017-01-04 Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71182
--- Comment #10 from Jakub Jelinek ---
Author: jakub
Date: Tue Jan 17 20:30:25 2017
New Revision: 244550
URL: https://gcc.gnu.org/viewcvs?rev=244550=gcc=rev
Log:
Backported from mainline
2017-01-04 Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78866
--- Comment #7 from Jakub Jelinek ---
Author: jakub
Date: Tue Jan 17 20:29:19 2017
New Revision: 244549
URL: https://gcc.gnu.org/viewcvs?rev=244549=gcc=rev
Log:
Backported from mainline
2016-12-21 Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79106
--- Comment #6 from Martin Sebor ---
That's right. I believe printing the contents of the translation unit and not
even opening the files referenced by the #line directives in it like Clang does
is the expected and correct behavior. Not just
On Tue, Jan 17, 2017 at 3:14 PM, Jason Merrill wrote:
> On Tue, Jan 17, 2017 at 1:20 PM, Nathan Sidwell wrote:
>> Jason,
>> in r241944:
>> 2016-11-07 Jason Merrill
>>
>> Implement P0012R1, Make exception specifications part of the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78488
Nathan Sidwell changed:
What|Removed |Added
Status|NEW |ASSIGNED
CC|
On Tue, Jan 17, 2017 at 1:20 PM, Nathan Sidwell wrote:
> Jason,
> in r241944:
> 2016-11-07 Jason Merrill
>
> Implement P0012R1, Make exception specifications part of the type
> system.
>
> You increment processing_template_decl around the
This patch implements propagation of PROP_gimple_lomp_dev during inlining to
allow using it to decide whether pass_omp_device_lower needs to run.
We need to clear this property in expand_omp_simd when the _simt_ clause is
present even if we are not doing any SIMT transforms, because we need to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69361
David Malcolm changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
This patch adds handling of new omp_simt_enter/omp_simt_exit named insns
in the NVPTX backend.
* config/nvptx/nvptx-protos.h (nvptx_output_simt_enter): Declare.
(nvptx_output_simt_exit): Declare.
* config/nvptx/nvptx.c (nvptx_init_unisimt_predicate): Use
This patch adjusts privatization in OpenMP SIMD loops lowered for SIMT targets.
Addressable private variables become fields of new '.omp_simt' structure that
is allocated by a call to GOMP_SIMT_ENTER (). This function is similar to
__builtin_alloca_with_align, except that it obtains per-SIMT-lane
This patch prevents inlining into SIMT code by introducing a new loop
property 'in_simtreg' and using ANNOTATE_EXPR (_, 'simtreg') to carry this
property between omp-low and the cfg pass (this is needed only for SIMD
reduction helper loops; for main bodies of SIMD loops omp-expand sets
In preparation to handle new SIMT privatization in lower_rec_simd_input_clauses
this patch factors out variables common to this and lower_rec_input_clauses to
a new structure. No functional change intended.
* omp-low.c (omplow_simd_context): New struct. Use it...
Hello,
This patch series addresses a correctness issue in how OpenMP SIMD regions are
transformed for SIMT execution. On NVPTX, OpenMP target code runs with
per-warp stacks outside of SIMD regions, and needs to transition to per-lane
stacks on SIMD region boundaries. Originally the plan was to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62314
David Malcolm changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71497
David Malcolm changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78469
Nathan Sidwell changed:
What|Removed |Added
Status|NEW |ASSIGNED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77629
Nathan Sidwell changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69481
--- Comment #15 from Nathan Sidwell ---
*** Bug 77629 has been marked as a duplicate of this bug. ***
On 01/17/2017 12:19 PM, Steve Silva via gcc wrote:
Hi All,
I am porting gcc for an internal processor and I am having some issues with
math instructions. Our processor uses two operands for math instructions which
are usually of the form OP0 = OP0 + OP1. The RTL pattern (for addm3) in gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79121
wilco at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
Hello!
As said above i386.c, inline_secondary_memory_needed:
--cut here--
The function can't work reliably when one of the CLASSES is a class
containing registers from multiple sets. We avoid this by never combining
different sets in a single alternative in the machine description.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77629
Nathan Sidwell changed:
What|Removed |Added
Status|NEW |ASSIGNED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71437
--- Comment #10 from amker at gcc dot gnu.org ---
(In reply to amker from comment #9)
> Root cause should be in VRP, looks like the iterative algorithm depends on
> order of ssa operands and computes different range.
Testing a patch, though is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78983
Damian Rouson changed:
What|Removed |Added
CC||damian at sourceryinstitute
dot or
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79121
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
Target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78478
--- Comment #13 from H.J. Lu ---
The problem is config/i386/rtemself.h has
#define LONG_DOUBLE_TYPE_SIZE (TARGET_80387 ? 80 : 64)
XFmode isn't available with -msoft-float even when -mlong-double-80 is used.
IA MCU defaults long double to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79121
Bug ID: 79121
Summary: [6, 7 regression] invalid expansion of sign-extend
unsigned plus left shift
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Keywords:
A left shift of 1 can always be done using an add, so slightly adjust rtx
cost for DImode left shift by 1 so that adddi3 is preferred in all cases,
and the arm_ashldi3_1bit is redundant.
DImode right shifts of 1 are rarely used (6 in total in the GCC binary),
so there is little benefit of the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79052
--- Comment #4 from Martin Sebor ---
Here's a complete set of warnings from a bootstrap configured with
--with-build-config=bootstrap-ubsan and --disable-werror. I think GCC builds
libraries without -Werror so those are probably not causing any
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78346
Jonathan Wakely changed:
What|Removed |Added
Known to work||4.8.5
Version|unknown
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79096
--- Comment #2 from physiker at toast2 dot net ---
> Am 16.01.2017 um 15:18 schrieb m.ostapenko at samsung dot com
> :
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79096
>
> Maxim Ostapenko changed:
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78478
--- Comment #12 from H.J. Lu ---
(In reply to Uroš Bizjak from comment #11)
> (In reply to Joel Sherrill from comment #9)
>
> > I could pursue this but is soft-float on the x86 target really worth the
> > investment of any effort? AFAIK we
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79120
Bug ID: 79120
Summary: lm32 ICE in dwarf2out_frame_debug_expr, at
dwarf2cfi.c:1747
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63741
Joel Sherrill changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63741
--- Comment #8 from Joel Sherrill ---
We are using gcc 4.9.3 for RTEMS 4.11 and gcc 6.3.0 on RTEMS 4.12. This doesn't
happen on either GCC. So closing.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79119
Martin Sebor changed:
What|Removed |Added
Keywords||missed-optimization
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79119
Bug ID: 79119
Summary: absolute value of a pointer difference can be assumed
to be less than or equal to PTRDIFF_MAX
Product: gcc
Version: 7.0
Status: UNCONFIRMED
On Jan 17, 2017, at 3:30 AM, Andrew Burgess wrote:
>
>> This patch revamps the arc's header file by means of using separate
>> headers for different tool targets. Each target header file holds the
>> specific compiler backend macros definitions. Thus, we have:
>> -
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79118
--- Comment #3 from Marek Polacek ---
The original preprocessed file started ICEing with -Wall -std=gnu++14 with
r219268:
In file included from
/mnt/g/boostish/outcome/test/../include/boost/outcome/v1.0/monad.hpp:98:0,
from
The attached patch adds fuchsia support to libgcc.
OK for trunk?
Thanks -
Josh
2017-01-17 Joshua Conner
* config/arm/unwind-arm.h (_Unwind_decode_typeinfo_ptr): Use
pc-relative indirect handling for fuchsia.
* config/t-slibgcc-fuchsia: New
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78952
--- Comment #3 from Segher Boessenkool ---
Note avr has an "any_extract" code_iterator for this. That of course
is a crutch but could be a workaround for you for now.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71437
--- Comment #9 from amker at gcc dot gnu.org ---
Root cause should be in VRP, looks like the iterative algorithm depends on
order of ssa operands and computes different range.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78839
Jakub Jelinek changed:
What|Removed |Added
Summary|[6/7 Regression] DWARF |[6 Regression] DWARF output
On Thu, Jan 12, 2017 at 2:36 AM, Markus Trippelsdorf
wrote:
> On 2017.01.11 at 13:03 +0100, Jakub Jelinek wrote:
>> On Wed, Jan 11, 2017 at 12:48:29PM +0100, Markus Trippelsdorf wrote:
>> > @@ -1965,7 +1966,11 @@ write_discriminator (const int discriminator)
>> >if
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78839
--- Comment #12 from Jakub Jelinek ---
Author: jakub
Date: Tue Jan 17 18:32:13 2017
New Revision: 244545
URL: https://gcc.gnu.org/viewcvs?rev=244545=gcc=rev
Log:
PR debug/78839
* dwarf2out.c (field_byte_offset): Restore the
On Thu, Jan 12, 2017 at 7:31 AM, Nathan Sidwell wrote:
> Thanks, that does address my comments. AFAICT your reading of the ABI doc
> is correct, but I'd like Jason to confirm that.
I agree.
> you're missing the testsuite/ChangeLog entry, don't forget.
I don't believe in
1 - 100 of 318 matches
Mail list logo