GCSE has some smarts to detect cases when a MEM appears in a block with
predecessor edges marked as EDGE_ABNORMAL. Such MEMs are removed from
the antic/transparent bitmaps.
Unfortunately this code did not work if the MEM was not the topmost RTX.
So something like (zero_extend (mem (...))
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78995
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78812
--- Comment #14 from Jeffrey A. Law ---
Author: law
Date: Thu Jan 5 07:38:48 2017
New Revision: 244093
URL: https://gcc.gnu.org/viewcvs?rev=244093=gcc=rev
Log:
PR tree-optimizatin/78812
* rtl.h (contains_mem_rtx_p): Prototype.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79000
Bug ID: 79000
Summary: ICE: in gen_member_die, at dwarf2out.c:23995
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Keywords: lto
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78999
Bug ID: 78999
Summary: problem with gcc on cygwin??? cygwin 2.6.1 with gcc
5.4.0
Product: gcc
Version: 5.4.0
Status: UNCONFIRMED
Severity: normal
On Fri, Dec 16, 2016 at 09:41:33AM -0500, Aldy Hernandez wrote:
> Hi folks.
>
> This is a follow-up on Jeff and Richi's interaction on the aforementioned PR
> here:
>
> https://gcc.gnu.org/ml/gcc-patches/2016-08/msg01397.html
>
> I decided to explore the idea of analyzing may-undefness
On Jan 4, 2017, Alexandre Oliva wrote:
> I'll prepare and post a patch anyway, but do we want to make it
> standard practice?
Here it is.
simplify_transformation_to_array had the nested loop unrolled 7 times,
which is reasonable given that it iterates over arrays of size
On Jan 4, 2017, Martin Sebor wrote:
> The manual recommends to use a length modifier to constrain the length
> of output to that of a narrower type:
> sprintf (xname, "", ((unsigned short)((uintptr_t)(t) & 0x)));
> This should work even without optimization.
It
On Jan 4, 2017, Alexandre Oliva wrote:
> So I guess we need some alternate PerFunction option flag that makes
> it per-function, but not part of the ICF hash?
Like this...
If we include them in the ICF hash, they may cause congruence_groups to
be processed in a different
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78914
Martin Sebor changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=16351
Martin Sebor changed:
What|Removed |Added
CC||msebor at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78998
Martin Sebor changed:
What|Removed |Added
Keywords||diagnostic
See Also|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78998
Bug ID: 78998
Summary: missing -Wnonnull for an unconditional call to strlen
with a null argument
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78996
Tim Shen changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78996
--- Comment #2 from Tim Shen ---
Author: timshen
Date: Thu Jan 5 03:18:17 2017
New Revision: 244092
URL: https://gcc.gnu.org/viewcvs?rev=244092=gcc=rev
Log:
2017-01-05 Tim Shen
PR libstdc++/78996
*
On Wed, Jan 4, 2017 at 7:16 PM, Tim Shen wrote:
> Since it's an obvious textual fix, I'm going to check it in directly.
Checked in with 80-columns limit respected. I have confusing tabstop
settings... :/
--
Regards,
Tim Shen
Since it's an obvious textual fix, I'm going to check it in directly.
--
Regards,
Tim Shen
commit b005916b043f52feed32b646f86ced80f3e5392b
Author: Tim Shen
Date: Wed Jan 4 19:07:07 2017 -0800
2017-01-05 Tim Shen
PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78987
Martin Sebor changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64767
--- Comment #11 from Eric Gallager ---
Thank you for adding this!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78948
Martin Sebor changed:
What|Removed |Added
Keywords||rejects-valid
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78988
Martin Sebor changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78997
Martin Sebor changed:
What|Removed |Added
Keywords||ice-on-valid-code
: posix
gcc version 7.0.0 20170104 (experimental) [trunk revision 244072] (GCC)
$
$ gcc-trunk -O2 small.c
$ gcc-6.2 -O3 small.c
$
$ gcc-trunk -O3 small.c
small.c: In function ‘foo’:
small.c:7:6: error: the first argument of a VEC_COND_EXPR must be of a boolean
vector type of the same number of elements
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78996
--- Comment #1 from W E Brown ---
Created attachment 40465
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40465=edit
Preprocessed source
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78996
Bug ID: 78996
Summary: uses macro as name
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78995
Bug ID: 78995
Summary: A strange copy error caused by O3 optimization
Product: gcc
Version: 4.8.5
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78823
--- Comment #3 from Michael Meissner ---
Author: meissner
Date: Thu Jan 5 00:43:53 2017
New Revision: 244084
URL: https://gcc.gnu.org/viewcvs?rev=244084=gcc=rev
Log:
[gcc]
2017-01-04 Michael Meissner
PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70568
--- Comment #8 from Michael Meissner ---
Author: meissner
Date: Thu Jan 5 00:43:53 2017
New Revision: 244084
URL: https://gcc.gnu.org/viewcvs?rev=244084=gcc=rev
Log:
[gcc]
2017-01-04 Michael Meissner
PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71977
--- Comment #4 from Michael Meissner ---
Author: meissner
Date: Thu Jan 5 00:43:53 2017
New Revision: 244084
URL: https://gcc.gnu.org/viewcvs?rev=244084=gcc=rev
Log:
[gcc]
2017-01-04 Michael Meissner
PR
On Wed, Jan 4, 2017 at 4:00 PM, Michael Meissner
wrote:
> On Wed, Jan 04, 2017 at 02:17:16PM -0500, David Edelsohn wrote:
>> The change to rs6000_emit_move() really should have been in a helper
>> function. We have to stop adding to the complexity of the function. I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=32415
bruno at clisp dot org changed:
What|Removed |Added
CC||bruno at clisp dot org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78993
--- Comment #4 from Andrew Pinski ---
# i_5 = PHI
# j_27 = PHI
# prephitmp_7 = PHI <0(3), prephitmp_17(4)>
_14 = i_5 > 9;
_18 = prephitmp_7 | _14;
if (_18 != 0)
goto ; [44.99%]
else
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78993
Martin Sebor changed:
What|Removed |Added
Known to fail||4.1.0, 5.3.0, 6.2.0, 7.0
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78993
Martin Sebor changed:
What|Removed |Added
Keywords||diagnostic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78812
--- Comment #13 from Jeffrey A. Law ---
So I see a case in postreload-gcse.c where we might mis-handle when the
destination is a ZERO_EXTRACT or STRICT_LOW_PART. Neither happen often which
is probably why we've never noticed.
On Tue, 11 Oct 2016, Nathan Sidwell wrote:
Update my email address
Did you mean to step down as
-type-safe vectors Nathan Sidwell
maintainer?
Unlike the other entries you modified, there is no + line with
your new address.
Gerald
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78994
--- Comment #3 from PeteVine ---
Hey, that works for me too! (62565 vs 70758 in favour of -Ofast). Usefully
strange :)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78812
--- Comment #12 from Jeffrey A. Law ---
I'm mostly concerned about other places where we assume that a memory reference
is supposed to show up at the toplevel of a source/dest.
For example, it looks like we don't properly handle the case where
On Thu, 10 Nov 2016, Richard Earnshaw wrote:
>> * gcc/config/aarch64/aarch64-cores.def (qdf24xx): Update part
>> number.
>> (falkor): New core.
> Installed. Please can you prepare a patch for the release notes as well.
In case you are wondering, Siddhesh, Richard was referring
to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78812
--- Comment #11 from Jakub Jelinek ---
(In reply to Jeffrey A. Law from comment #10)
> Since that's not a MEM_P, the expression isn't removed from antic/transp
> which makes it subject to hoisting across the abnormal edge.
>
> This could be
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78989
Andrew Pinski changed:
What|Removed |Added
Depends on||77513
--- Comment #6 from Andrew Pinski
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78989
--- Comment #5 from Andrew Pinski ---
Isn't there a dup somewhere? I Know this was filed before.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78812
Jeffrey A. Law changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |law at redhat dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60685
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78994
Andrew Pinski changed:
What|Removed |Added
Summary|-Ofast makes aarch64 C++|-Ofast makes aarch64 C++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78994
Andrew Pinski changed:
What|Removed |Added
URL|https://github.com/supercur |
|io/dsp-bench-cpp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78994
Bug ID: 78994
Summary: -Ofast makes aarch64 C++ benchmark slower
Product: gcc
Version: 5.4.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78991
Tobias changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
On Wed, Jan 04, 2017 at 04:24:55PM -0500, Jason Merrill wrote:
> On Mon, Jan 2, 2017 at 2:32 PM, Jakub Jelinek wrote:
> > if (TREE_CODE (type) == REFERENCE_TYPE)
> > {
> > - error ("in C++98 %q+D may not have reference type %qT "
> > -
On Wed, Jan 04, 2017 at 04:27:42PM -0500, Jason Merrill wrote:
> On Thu, Dec 29, 2016 at 10:11 AM, Jakub Jelinek wrote:
> > probe = TREE_OPERAND (probe, 0);
> > TREE_TYPE (v[i]) = TREE_TYPE (probe);
> > layout_decl (v[i], 0);
> > -
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78991
--- Comment #2 from Tobias ---
Thanks. The evidence you collected shows quite clear, that it probably is a
problem with clang.
So I now posted it here: https://llvm.org/bugs/show_bug.cgi?id=31537
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64767
Marek Polacek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64767
--- Comment #9 from Marek Polacek ---
Author: mpolacek
Date: Wed Jan 4 21:47:04 2017
New Revision: 244076
URL: https://gcc.gnu.org/viewcvs?rev=244076=gcc=rev
Log:
PR c++/64767
* c.opt (Wpointer-compare): New option.
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78910
Martin Sebor changed:
What|Removed |Added
Keywords||patch
--- Comment #2 from Martin Sebor
The attached patch corrects an off-by-one mistake in handling
non-zero precisions in signed conversions (%d and %i) with
negative arguments, such as in sprintf(d, "%.2", -1). The call
which results in the three bytes "-01" on output, not 2. I.e.,
the minus sign must be taken into consideration.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78991
--- Comment #1 from Andrew Pinski ---
How positive you are that this is a libstdc++ bug rather than a clang bug? It
works correctly with GCC 5.4.0's front-end and GCC 7.0's libstdc++ and
front-end.
On Wed, 2017-01-04 at 09:04 -0700, Jeff Law wrote:
> On 01/04/2017 06:42 AM, Jason Merrill wrote:
> > On Wed, Jan 4, 2017 at 8:13 AM, Alexandre Oliva
> > wrote:
> > > On Jan 3, 2017, Jason Merrill wrote:
> > >
> > > > Are there bugzillas for these false
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78993
--- Comment #1 from David Malcolm ---
Created attachment 40462
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40462=edit
Gimple dump from when warning is emitted
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78949
--- Comment #7 from Jakub Jelinek ---
Fixed on the trunk so far.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78693
Jakub Jelinek changed:
What|Removed |Added
Summary|[6/7 Regression] Bogus |[6 Regression] Bogus
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78993
Bug ID: 78993
Summary: False positive from -Wmaybe-uninitialized
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
On Dec 14, 2016, Alexandre Oliva wrote:
> On Oct 19, 2016, Alexandre Oliva wrote:
>> On Sep 23, 2016, Alexandre Oliva wrote:
>>> This patchset adds support for the C++ language to libcc1.
>>> It updates a few patches for libcc1 by Jan
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78949
--- Comment #6 from Jakub Jelinek ---
Author: jakub
Date: Wed Jan 4 21:34:27 2017
New Revision: 244075
URL: https://gcc.gnu.org/viewcvs?rev=244075=gcc=rev
Log:
PR c++/78949
* typeck.c (cp_build_unary_op): Call mark_rvalue_use
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78693
--- Comment #5 from Jakub Jelinek ---
Author: jakub
Date: Wed Jan 4 21:30:35 2017
New Revision: 244074
URL: https://gcc.gnu.org/viewcvs?rev=244074=gcc=rev
Log:
PR c++/78693
* parser.c (cp_parser_simple_declaration): Only
On Thu, Dec 29, 2016 at 10:11 AM, Jakub Jelinek wrote:
> probe = TREE_OPERAND (probe, 0);
> TREE_TYPE (v[i]) = TREE_TYPE (probe);
> layout_decl (v[i], 0);
> - SET_DECL_VALUE_EXPR (v[i], tt);
> + SET_DECL_VALUE_EXPR (v[i],
OK.
On Thu, Dec 29, 2016 at 10:19 AM, Jakub Jelinek wrote:
> Hi!
>
> For integral arg, mark_exp_read is called during
> cp_perform_integral_promotions, for complex type it is called during
> cp_default_conversion, but for vector types nothing actually calls it.
>
> Fixed
On Mon, Jan 2, 2017 at 2:32 PM, Jakub Jelinek wrote:
> if (TREE_CODE (type) == REFERENCE_TYPE)
> {
> - error ("in C++98 %q+D may not have reference type %qT "
> -"because it is a member of a union", x, type);
> -
OK.
On Mon, Jan 2, 2017 at 3:11 PM, Jakub Jelinek wrote:
> Hi!
>
> As the testcase shows, if some initializers are type dependent, auto_result
> is still using auto, is not yet deduced and the deduction will happen during
> instantiation. So rejecting it due to inconsistent
On Jan 4, 2017, Richard Biener wrote:
>> Unfortunately I don't have another that silences the warning without
>> (or even with) impact on codegen.
> #pragma GCC diagnostic push ("Wno-array-bounds")
> #pragma GCC diagnostic pop
Wwwhaaat? #pragma GCC diagnostic to
On Wed, 4 Jan 2017, Marek Polacek wrote:
> Bootstrapped/regtested on x86_64-linux, ok for trunk?
The C changes are OK.
--
Joseph S. Myers
jos...@codesourcery.com
On Wed, 4 Jan 2017, Jakub Jelinek wrote:
> On Wed, Jan 04, 2017 at 01:31:28PM +0100, Richard Biener wrote:
> > > Rather than implicit RejectNegative it might be better to just diagnose
> > > such options as invalid. If you agree, I can implement that as follow-up.
> > > Also note that
On Mon, 14 Nov 2016, Martin Liška wrote:
> Following patch adds TAB settings to contrib/vimrc file.
> Hope it looks reasonable?
This does not appear applied, are you waiting for approval? If
so, for something like this in contrib we don't need to get overly
strict and I'd say go ahead.
On Wed, Jan 04, 2017 at 01:31:28PM +0100, Richard Biener wrote:
> > And not sure why this actually
> > is RejectNegative, wouldn't
> > Common Alias(fvect-cost-model=,dynamic,unlimited)
> > work just on fvect-cost-model (can test that)?
>
> Good question ;) If it works, ok.
And here is a patch
On Wed, Jan 04, 2017 at 01:31:28PM +0100, Richard Biener wrote:
> > Rather than implicit RejectNegative it might be better to just diagnose
> > such options as invalid. If you agree, I can implement that as follow-up.
> > Also note that RejectNegative is only needed on the Enum switches that have
On Wed, Jan 04, 2017 at 08:56:07PM +, James Clarke wrote:
> libsanitizer:
> PR sanitizer/78992
> * sanitizer_common/sanitizer_platform_limits_posix.h: sigaction
> should only have __glibc_reserved0 as a member on 64-bit sparc.
It should be committed upstream first and then
On Wed, Jan 4, 2017 at 1:19 PM, Marek Polacek wrote:
> +Note that the code above is illegal in C++11.
"invalid". The C++ changes are OK.
Jason
On Wed, Jan 04, 2017 at 02:17:16PM -0500, David Edelsohn wrote:
> The change to rs6000_emit_move() really should have been in a helper
> function. We have to stop adding to the complexity of the function. I
> won't insist that you split it out, but any addition of more than a
> few lines in
OK.
Jason
On Wed, Jan 4, 2017 at 11:44 AM, Nathan Sidwell wrote:
> On 01/04/2017 10:13 AM, Jason Merrill wrote:
>
>> OK, that looks like the problem; we shouldn't be calling
>> maybe_constant_value before we perform the conversion.
>
>
> Yup, that worked.
>
>
> ok?
>
> nathan
>
libsanitizer:
PR sanitizer/78992
* sanitizer_common/sanitizer_platform_limits_posix.h: sigaction
should only have __glibc_reserved0 as a member on 64-bit sparc.
---
libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.h | 7 +--
1 file changed, 5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78992
Bug ID: 78992
Summary: Incorrect sigaction definition on 32-bit sparc
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78116
--- Comment #10 from Pat Haugen ---
(In reply to Jakub Jelinek from comment #9)
> Any progress on this?
Besides waiting for pr77536 to be fixed, I'm not sure what specifically can be
done on this issue to fix the problem. I personally have not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78991
Bug ID: 78991
Summary: std::sort and std::unique can not use std::function
with clang++ -std=c++14
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78957
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78957
--- Comment #2 from Jakub Jelinek ---
Author: jakub
Date: Wed Jan 4 20:25:13 2017
New Revision: 244072
URL: https://gcc.gnu.org/viewcvs?rev=244072=gcc=rev
Log:
PR driver/78957
* c.opt (fsso-struct=): Add RejectNegative.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71182
Jakub Jelinek changed:
What|Removed |Added
Summary|[6/7 Regression] parser.c |[6 Regression] parser.c
On Wed, Jan 04, 2017 at 02:17:16PM -0500, David Edelsohn wrote:
> On Thu, Dec 29, 2016 at 7:24 PM, Michael Meissner
> wrote:
>
> Mike,
>
> Thanks for the tremendous effort on this patch. A few comments.
>
> The ChangeLog contains a lot of extraneous commentary
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71182
--- Comment #8 from Jakub Jelinek ---
Author: jakub
Date: Wed Jan 4 20:05:14 2017
New Revision: 244070
URL: https://gcc.gnu.org/viewcvs?rev=244070=gcc=rev
Log:
PR c++/71182
* parser.c (cp_lexer_previous_token): Use
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78953
Michael Meissner changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78900
--- Comment #3 from Michael Meissner ---
Fixed in trunk in subversion id 244044. I will hold the bug open until it is
checked into the GCC 6 branch.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78056
--- Comment #20 from kelvin at gcc dot gnu.org ---
Author: kelvin
Date: Wed Jan 4 20:03:00 2017
New Revision: 244068
URL: https://gcc.gnu.org/viewcvs?rev=244068=gcc=rev
Log:
gcc/testsuite/ChangeLog:
2017-01-04 Kelvin Nilsen
On Tue, Jan 3, 2017 at 8:28 PM, David Malcolm wrote:
> PR c++/77829 and PR c++/78656 identify an issue within the C++ frontend
> where it issues nonsensical fix-it hints for misspelled name lookups
> within an explicitly given namespace: it finds the closest name within
> all
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78989
--- Comment #4 from David Malcolm ---
...or to use a rich location to send two locations for the warning, giving:
return (asan_poison_variables &&
^~
# 6 "gimplify.cpp" 3 4
__null
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78989
--- Comment #3 from David Malcolm ---
Looking at the PRs you filed about the locations (PR78987 and PR78988), perhaps
the best approach here is for the location of the warning to be either this:
return (asan_poison_variables &&
OK.
On Tue, Jan 3, 2017 at 6:15 PM, Jakub Jelinek wrote:
> Hi!
>
> http://dwarfstd.org/ShowIssue.php?issue=161102.1
> got accepted today, so DWARF5 is going to use uleb128 sizes instead of
> 2-byte sizes in .debug_loclists section.
> On a randomly chosen *.i file I had around,
OK.
On Tue, Jan 3, 2017 at 5:42 PM, Jakub Jelinek wrote:
> Hi!
>
> cp_lexer_new_from_tokens creates lexer that has NULL lexer->buffer,
> calling lexer->buffer->address () therefore is UB (diagnosed by
> --with-boot-config=bootstrap-ubsan).
>
> The following patch fixes this, or
On Tue, Jan 3, 2017 at 5:39 PM, Jakub Jelinek wrote:
> + if (auto_function_declaration
> + && (TREE_CODE (decl) == FUNCTION_DECL
> + || auto_function_declaration != error_mark_node))
> + {
> + error_at
On 01/04/2017 12:18 PM, Segher Boessenkool wrote:
On Wed, Jan 04, 2017 at 06:42:23PM +, Richard Sandiford wrote:
1. reload has a bug that no-one really wants to fix (understandable)
2. the bug is triggered by paradoxical subregs of mems
3. those subregs are normally disabled on targets that
On 01/04/2017 11:01 AM, Jakub Jelinek wrote:
On Wed, Jan 04, 2017 at 11:19:46AM +0100, Richard Biener wrote:
For the SSA_NAME + INTEGER_CST case restrict it to the case
if (x_1 > 5)
tem_2 = (char) x_1;
# tem_3 = PHI
that is, (char) x_1 uses x_1 and that also appears in the
On 01/04/2017 11:55 AM, Jeff Law wrote:
On 12/09/2016 01:28 AM, Richard Biener wrote:
On Wed, Dec 7, 2016 at 12:18 AM, Jeff Law wrote:
So I was going through the various DSE related bugs as stumbled across
67955.
The basic issue in 67955 is that DSE is too simplistic when
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67955
--- Comment #11 from Jeffrey A. Law ---
Author: law
Date: Wed Jan 4 19:22:44 2017
New Revision: 244067
URL: https://gcc.gnu.org/viewcvs?rev=244067=gcc=rev
Log:
PR tree-optimizatin/67955
* tree-ssa-alias.c
1 - 100 of 263 matches
Mail list logo