On Thu, 12 Jul 2018 at 19:01, Pedro Alves wrote:
>
> On 07/12/2018 05:17 PM, Richard Sandiford wrote:
> > Pedro Alves writes:
>
> >> (an
> >>> alternative to pointers is to return a struct with the wide int result
> >>> and the overflow flag),
> >>
> >> +1. I've been pushing GDB in that
On 07/12/2018 04:41 AM, Richard Sandiford wrote:
Following on from:
https://gcc.gnu.org/ml/gcc-patches/2018-07/msg00603.html
this patch is an RFC to mention references in the C++ coding conventions.
It allows const references anywhere they're useful but only allows
non-constant references
I tried to rebuild for target pdp11 with fortran enabled (in the past I've just
enabled C). It builds fine but the resulting compiler crashes at startup:
Paul-Konings-MacBook-Pro:gcc pkoning$ ./xgcc -B. -O2 -S ../../hello.f
f951: internal compiler error: gfc_validate_kind(): Got bad kind
On 07/12/2018 05:17 PM, Richard Sandiford wrote:
> Pedro Alves writes:
>> (an
>>> alternative to pointers is to return a struct with the wide int result
>>> and the overflow flag),
>>
>> +1. I've been pushing GDB in that direction whenever possible.
>
> I agree that can sometimes be better. I
Snapshot gcc-7-20180712 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/7-20180712/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 7 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-7
Thank you Jakub ,the attached patch in the PR86492 fixes the issue.
Appreciate your quick response here .
~Umesh
On Wed, Jul 11, 2018 at 10:17 PM, Jakub Jelinek wrote:
> On Wed, Jul 11, 2018 at 09:48:07PM +0530, Umesh Kalappa wrote:
>> Cc'ed Kyrill.
>
> Mailing list is not the right medium to
Hi,
this is a heads-up that configuring with --enable-maintainer-mode
currently breaks bootstrap; see
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86450
for details.
Running configure with --enable-maintainer-mode --disable-werror
allows bootstrap to proceed until the underlying issue is
On 07/12/2018 12:40 PM, Jonathan Wakely wrote:
> On Thu, 12 Jul 2018 at 11:41, Richard Sandiford wrote:
>> +Only use non-constant references in the following situations:
>> +
>> +
>> +
>> +when they are necessary to conform to a standard interface, such as
>> +the first argument to a non-member
Following on from:
https://gcc.gnu.org/ml/gcc-patches/2018-07/msg00603.html
this patch is an RFC to mention references in the C++ coding conventions.
It allows const references anywhere they're useful but only allows
non-constant references in contexts that conform to a standard
interface,
On Thu, Jul 12, 2018 at 12:41 PM Richard Sandiford
wrote:
>
> Following on from:
>
> https://gcc.gnu.org/ml/gcc-patches/2018-07/msg00603.html
>
> this patch is an RFC to mention references in the C++ coding conventions.
> It allows const references anywhere they're useful but only allows
>
On Thu, 12 Jul 2018 at 11:41, Richard Sandiford wrote:
> +Only use non-constant references in the following situations:
> +
> +
> +
> +when they are necessary to conform to a standard interface, such as
> +the first argument to a non-member operator+=
And the return value of such operators (which
Hi everyone,
we have our source base ,that was compiled for armv7 on gcc8.1 with
soft-float and for following input
a=0x0010
b=0x0001
result = a - b ;
we are getting the result as "0x000e" and with
-mhard-float (disabled the flush to zero mode ) we are
On 12/07/18 16:20, Umesh Kalappa wrote:
Hi everyone,
we have our source base ,that was compiled for armv7 on gcc8.1 with
soft-float and for following input
a=0x0010
b=0x0001
result = a - b ;
we are getting the result as "0x000e" and with
-mhard-float
Status
==
The GCC 8 branch is open for regression and documentation fixes. We
intend to release GCC 8.2 soon starting with a release candidate
mid to end of next week. This gives you some time to go over your
assigned regression bug reports and consider backports.
There is currently one
Pedro Alves writes:
> On 07/12/2018 12:40 PM, Jonathan Wakely wrote:
>> On Thu, 12 Jul 2018 at 11:41, Richard Sandiford wrote:
>>> +Only use non-constant references in the following situations:
>>> +
>>> +
>>> +
>>> +when they are necessary to conform to a standard interface, such as
>>> +the
> On Jul 12, 2018, at 1:42 PM, Jeff Law wrote:
>
> On 07/12/2018 11:17 AM, Paul Koning wrote:
>>
>>
>>> On Jul 12, 2018, at 12:55 PM, Jeff Law wrote:
>>>
>>> On 07/11/2018 06:20 PM, Paul Koning wrote:
This patch removes the obsolete documentation for
Hi!
As the following testcases show, diagnosing non-mappable type already in
c*_decl_attributes is too early, the type might not be finalized and
completed at that point for some variables yet.
This patch defers it until *finish_decl. Bootstrapped/regtested on
x86_64-linux and i686-linux,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43064
David Malcolm changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
Hi!
On Tue, Jul 10, 2018 at 12:10:51PM -0500, Will Schmidt wrote:
> Add support for Gimple folding for unaligned vector loads and stores.
This is fine if the experts agree. Thanks! And thanks to the reviewers,
too.
One detail:
> * config/rs6000/rs6000.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85974
Martin Sebor changed:
What|Removed |Added
CC||msebor at gcc dot gnu.org
--- Comment #4
Hi all,
here is a minor update of the patch, which cures some problems with
implicitly pure functions in the previous version.
Most implicitly pure functions were actually detected correctly, but
implicitly pure functions that called other implicitly pure functions
were not detected properly,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86490
--- Comment #9 from zenith432 at users dot sourceforge.net ---
It is worth studying what gold is doing, because it's not just skipping the
object files in the archives.
If you link with
gcc -flto -save-temps -fuse-ld=gold -o x main.o libfoo.a
Ping: https://gcc.gnu.org/ml/gcc-patches/2018-07/msg00197.html
On 07/04/18 12:53, Bernd Edlinger wrote:
> Hi,
>
> currently _Pragma("GCC diagnostic ...") does not properly
> work in macro expansions.
>
> Consider the following code:
>
> #define B _Pragma("GCC diagnostic push") \
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86509
--- Comment #1 from Uroš Bizjak ---
Ops, no, the above is with gcc-7.3.
gcc-9 correctly emits:
x.0_1 ={v} x;
_2 = x.0_1 u<=
1.79769313486231570814527423731704356798070567525844996599e+308;
_3 = (int) _2;
i ={v} _3;
_4 = fetestexcept
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86503
--- Comment #2 from Jonathan Wakely ---
(In reply to Richard Biener from comment #1)
> You run out of memory or stack. Try ulimit -s unlimited
Yes but that seems to be because GCC goes into an infinte recursive
instantiation, which it
Hi Janus,
The cleaner approach would certainly be to avoid short-circuiting of
impure functions altogether. If we can all agree that this is a good
idea,
This is a fine example of logical short-circuiting - the condition you
mention is false, therefore the rest need not be evaluated :-)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86510
Bug ID: 86510
Summary: [9 regression] test case g++.dg/warn/pr86453.C fails
starting with r262596
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86511
Andrew Pinski changed:
What|Removed |Added
Target|alphaev68-linux-gnu |
--- Comment #1 from Andrew Pinski ---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53769
Florian Weimer changed:
What|Removed |Added
CC||fw at gcc dot gnu.org
--- Comment #7
This fixes a typo in the output of a ".set" directive.
Committed.
paul
ChangeLog:
2018-07-12 Paul Koning
* config/pdp11/pdp11.c (pdp11_output_def): Fix typo in .set
directive.
Index: config/pdp11/pdp11.c
2018-07-12 21:53 GMT+02:00 Thomas Koenig :
> Hi Janus,
>
>> The cleaner approach would certainly be to avoid short-circuiting of
>> impure functions altogether. If we can all agree that this is a good
>> idea,
>
>
> This is a fine example of logical short-circuiting - the condition you
> mention
This eliminates one Ada testsuite failure, by adding riscv*-*-* for the list
of targets that expect this warning. This was pre-approved by Eric Botcazou.
Tested with a riscv64-linux native Ada testsuite run. There was one less
failure with this patch.
Committed.
Jim
gcc/testsuite/
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86509
Bug ID: 86509
Summary: Invalid conversion of comparison with infinity
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
r259399, which added PROCESSOR_SKYLAKE, disabled many x86 optimizations
which are enabled by PROCESSOR_HASWELL. As the result, -mtune=skylake
generates slower codes on Skylake than before. The same also applies
to Cannonlake and Icelak tuning.
This patch changes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86507
--- Comment #3 from Jonathan Wakely ---
(In reply to tower120 from comment #0)
> All 7.x with
> "experimental/filesystem" worked fine.
Are you sure about that? You might be able to include the header, but nothing
else works.
Anyway, this is an
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86511
Bug ID: 86511
Summary: Unordered comparisons are expanded with branchless
code
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
On Thu, Jul 12, 2018 at 7:53 AM, Kito Cheng wrote:
> ping.
> On Fri, Jul 6, 2018 at 4:38 PM Kito Cheng wrote:
>>
>> Hi all:
>>
>> This patch implemented TARGET_MERGE_DECL_ATTRIBUTES hook to check the
>> interrupter is all compatible, tested with rv32ima and rv64ima elf
>> toolchain.
>>
>>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86509
Uroš Bizjak changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
A somewhat old "issue report" pointed me to the code generated for a 4-fold
manually unrolled version of the following loop:
> while (++len != len_limit) /* this is loop */
> if (pb[len] != cur[len])
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86510
--- Comment #1 from Martin Sebor ---
Author: msebor
Date: Thu Jul 12 22:42:00 2018
New Revision: 262609
URL: https://gcc.gnu.org/viewcvs?rev=262609=gcc=rev
Log:
PR testsuite/86510 - test case g++.dg/warn/pr86453.C fails starting with
r262596
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86471
--- Comment #7 from Andrew Pinski ---
(In reply to Matt Bentley from comment #6)
> Suggested patch for libstdc++, std_algobase.h, line 688:
> template
> inline typename
> __gnu_cxx::__enable_if<__is_scalar<_Tp>::__value, void>::__type
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86510
Martin Sebor changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86259
--- Comment #21 from Davin McCall ---
Looking at this further, the proposal actually states, for the address-of
operator:
> When the operand designates an object, the result has the single provenance
> of the outermost object containing that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86471
--- Comment #8 from Matt Bentley ---
> This is incorrect for floating point types and non scalars. And it
> introduces an extra check at runtime if value is not known to compile time.
This is the overload for scalar types, read the function
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86259
--- Comment #22 from Martin Sebor ---
In areas where the authors of the proposal find the standard open to
interpretation and when they feel it doesn't contradict the surveyed
implementation practice they tend to suggest to tighten the
On Thu, 2018-07-12 at 07:17 +0100, Richard Sandiford wrote:
>
> So it only calls targetm.hard_regno_call_part_clobbered if such a
> call is known to exist somewhere between the two references to
> regno (although we don't have the calls themselves to hand).
>
> Thanks,
> Richard
Having the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86471
--- Comment #6 from Matt Bentley ---
Suggested patch for libstdc++, std_algobase.h, line 688:
template
inline typename
__gnu_cxx::__enable_if<__is_scalar<_Tp>::__value, void>::__type
__fill_a(_ForwardIterator __first,
On Thu, Jul 12, 2018 at 8:56 AM, Pierre-Marie de Rodat
wrote:
> I don’t have much more to say than debug11.adb’s comment ;-)
>
>> This testcase checks that in the DWARF description of the variant type
>> below, the C discriminant is properly described as unsigned, hence the
>> 0x5a
>> ('Z') and
On Fri, 29 Jun 2018, Kyrill Tkachov wrote:
> This patch adds support for the Arm Cortex-A76 processor in changes.html
> for GCC 9. It enables the AArch64 section of the page and adds the news
> blob there. It also adds an entry to the already-existing arm entry.
Thank you, Kyrill.
Should I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86489
--- Comment #7 from kugan at gcc dot gnu.org ---
Author: kugan
Date: Fri Jul 13 05:25:47 2018
New Revision: 262622
URL: https://gcc.gnu.org/viewcvs?rev=262622=gcc=rev
Log:
gcc/ChangeLog:
2018-07-13 Kugan Vivekanandarajah
Richard
On 07/13/2018 01:57 AM, Jim Wilson wrote:
I poked at this a little and noticed a difference between the x86_64
support and the RISC-V support. The RISC-V C language port has char
as unsigned by default. The x86_64 port has char signed by default.
If I add a -fsigned-char option, then the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86479
--- Comment #4 from Richard Biener ---
Author: rguenth
Date: Thu Jul 12 07:11:50 2018
New Revision: 262574
URL: https://gcc.gnu.org/viewcvs?rev=262574=gcc=rev
Log:
2018-07-12 Richard Biener
PR middle-end/86479
* fold-const.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86480
Richard Biener changed:
What|Removed |Added
Priority|P3 |P2
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86504
--- Comment #1 from Jiangning Liu ---
Created attachment 44387
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44387=edit
bad vectorizatoin result for boundary size 8
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86506
Bug ID: 86506
Summary: tree-vect-patterns.c:225: shift too large for type ?
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
On Wed, 11 Jul 2018, Martin Sebor wrote:
> The attached change set adjusts the attribute exclusion code
> to detect and reject incompatible attributes before attribute
> handlers are called to have a chance to make changes despite
> the exclusions. The handlers are not run when a conflict is
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86504
Richard Biener changed:
What|Removed |Added
Target||arm
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86471
--- Comment #5 from Matt Bentley ---
What would be even more useful is a warning: for unused data.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86504
Bug ID: 86504
Summary: vectorization failure for a nest loop
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86492
--- Comment #5 from Jakub Jelinek ---
Author: jakub
Date: Thu Jul 12 07:46:04 2018
New Revision: 262577
URL: https://gcc.gnu.org/viewcvs?rev=262577=gcc=rev
Log:
PR tree-optimization/86492
* gimple-ssa-store-merging.c
On 07/11/2018 01:33 PM, Richard Sandiford wrote:
Aldy Hernandez writes:
On 07/11/2018 08:52 AM, Richard Biener wrote:
On Wed, Jul 11, 2018 at 8:48 AM Aldy Hernandez wrote:
Hmmm, I think we can do better, and since this hasn't been reviewed yet,
I don't think anyone will mind the adjustment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86492
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
On 07/12/2018 04:29 AM, Richard Sandiford wrote:
Aldy Hernandez writes:
On 07/11/2018 01:33 PM, Richard Sandiford wrote:
Aldy Hernandez writes:
On 07/11/2018 08:52 AM, Richard Biener wrote:
On Wed, Jul 11, 2018 at 8:48 AM Aldy Hernandez wrote:
Hmmm, I think we can do better, and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86489
--- Comment #2 from Richard Biener ---
gimple *phi = SSA_NAME_DEF_STMT (b_11);
if (gimple_code (phi) != GIMPLE_PHI
|| (gimple_assign_lhs (and_stmt)
!= gimple_phi_arg_def (phi, loop_latch_edge (loop)->dest_idx)))
return
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86497
Richard Biener changed:
What|Removed |Added
Priority|P3 |P2
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86505
Richard Biener changed:
What|Removed |Added
Priority|P3 |P2
Status|UNCONFIRMED
The following fixes fold_binary_op_with_conditional_arg to not move
a possibly trapping operation into the conditional arms because
this breaks later re-gimplification and also because we lose
information this way (like dividend is nonzero on the unconditional path).
Bootstrapped and tested on
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59859
Bug 59859 depends on bug 86479, which changed state.
Bug 86479 Summary: [9 Regression] [graphite] ICE in gimplify_modify_expr, at
gimplify.c:5756
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86479
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86479
Richard Biener changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86453
Richard Biener changed:
What|Removed |Added
Keywords|patch |
Component|middle-end
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86453
--- Comment #12 from Richard Biener ---
Author: rguenth
Date: Thu Jul 12 07:13:36 2018
New Revision: 262575
URL: https://gcc.gnu.org/viewcvs?rev=262575=gcc=rev
Log:
2018-07-12 Richard Biener
PR c/86453
* c-attribs.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86492
--- Comment #4 from Jakub Jelinek ---
Author: jakub
Date: Thu Jul 12 07:39:33 2018
New Revision: 262576
URL: https://gcc.gnu.org/viewcvs?rev=262576=gcc=rev
Log:
PR tree-optimization/86492
* gimple-ssa-store-merging.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86495
Richard Biener changed:
What|Removed |Added
Keywords||diagnostic
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86503
--- Comment #1 from Richard Biener ---
You run out of memory or stack. Try ulimit -s unlimited
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86506
--- Comment #1 from David Binderman ---
$ ~/gcc/results.262549.ubsan/bin/gcc -c -O3 bug450.c
bug450.c: In function ‘b’:
bug450.c:5:21: warning: assignment to ‘int’ from ‘void (*)()’ makes integer
from pointer without a cast [-Wint-conversion]
Jeff Law writes:
> On 07/11/2018 02:07 PM, Steve Ellcey wrote:
>> I have a reload/register allocation question and possible patch. While
>> working on the Aarch64 SIMD ABI[1] I ran into a problem where GCC was
>> saving and restoring registers that it did not need to. I tracked it
>> down to
This moves a recursion limit installed for PR80887 from
vn_lookup_simplify_result to gimple_resimplify* where it also applies
to a testcase I'm running into with modified VN without ever
calling vn_lookup_simplify_result. Basically with VN we are
not presenting the match.pd patterns with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86505
Bug ID: 86505
Summary: __builtin_va_arg_pack_len() computes the number of
arguments wrongly
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86504
ktkachov at gcc dot gnu.org changed:
What|Removed |Added
Keywords||missed-optimization
Aldy Hernandez writes:
> On 07/11/2018 01:33 PM, Richard Sandiford wrote:
>> Aldy Hernandez writes:
>>> On 07/11/2018 08:52 AM, Richard Biener wrote:
On Wed, Jul 11, 2018 at 8:48 AM Aldy Hernandez wrote:
>
> Hmmm, I think we can do better, and since this hasn't been reviewed yet,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86506
David Binderman changed:
What|Removed |Added
CC||rsandifo at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86450
--- Comment #21 from Thomas Koenig ---
(In reply to Jonathan Wakely from comment #20)
> For libstdc++ the default (without --enable-werror or --disable-werror) is
> to add $(WERROR_FLAG) to WARN_FLAGS. WERROR_FLAG is empty by default, but
>
Hi,
this is a heads-up that configuring with --enable-maintainer-mode
currently breaks bootstrap; see
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86450
for details.
Running configure with --enable-maintainer-mode --disable-werror
allows bootstrap to proceed until the underlying issue is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80122
Richard Biener changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
On Thu, 12 Jul 2018, Jakub Jelinek wrote:
> Hi!
>
> The following testcase is a similar issue to PR84503 and the fix is similar,
> because coalesce_immediate_stores temporarily sorts the stores on ascending
> bitpos and if stores are merged, the merged store is emitted in the location
> of the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80122
--- Comment #14 from rpirrera at aitek dot it ---
(In reply to Richard Biener from comment #13)
> Can you please open a new bugreport? Btw, your snippet doesn't compile
> because you miss ANSI_BOLD and friends, removing it and adding a #include
Hi,
It can be useful to print the number of tests in each category, eg:
Tests that now work, but didn't before (65 tests):
instead of
Tests that now work, but didn't before:
This small patch does that.
OK?
Thanks,
Christophe
contrib/ChangeLog:
2018-07-12 Christophe Lyon
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86496
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |9.0
Hi Jackson
On 11/07/18 17:48, Jackson Woodruff wrote:
Hi Sudi,
Thanks for the review.
On 07/10/2018 10:56 AM, Sudakshina wrote:
Hi Jackson
- if (!MEM_P (mem_1) || aarch64_mem_pair_operand (mem_1, mode))
+ if (!MEM_P (mem[1]) || aarch64_mem_pair_operand (mem[1], mode))
mem_1 == mem[1]?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86462
Richard Biener changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment
Hi Jackson
On 11/07/18 17:48, Jackson Woodruff wrote:
Hi Sudi,
On 07/10/2018 02:29 PM, Sudakshina Das wrote:
Hi Jackson
On Tuesday 10 July 2018 09:37 AM, Jackson Woodruff wrote:
Hi all,
This patch resolves PR86014. It does so by noticing that the last
load may clobber the address
On 07/11/2018 05:40 PM, Robin Dapp wrote:
Hi,
the following patch increases the default function alignment to 16
bytes. This helps get rid of some unwanted performance effects.
I'm unsure whether or when it's necessary to implement
OVERRIDE_OPTIONS_AFTER_CHANGE.
Hi.
Yes, it's how that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86468
Dominique d'Humieres changed:
What|Removed |Added
Keywords||ice-on-valid-code
On Thu, 12 Jul 2018, Jakub Jelinek wrote:
> On Thu, Jul 12, 2018 at 12:29:20PM +0200, Richard Biener wrote:
> > After my PR86413 fix to always annotate existing lexical block DIEs with
> > range attributes debuginfo grows significantly in case we previously
> > had "stale" lexical block DIEs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86462
--- Comment #6 from Richard Biener ---
Author: rguenth
Date: Thu Jul 12 12:32:30 2018
New Revision: 262583
URL: https://gcc.gnu.org/viewcvs?rev=262583=gcc=rev
Log:
2018-07-12 Richard Biener
PR debug/86462
* dwarf2out.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86462
Richard Biener changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84829
--- Comment #17 from Richard Biener ---
Author: rguenth
Date: Thu Jul 12 12:47:48 2018
New Revision: 262584
URL: https://gcc.gnu.org/viewcvs?rev=262584=gcc=rev
Log:
2018-07-12 Richard Biener
PR target/84829
*
Richard Biener writes:
> On Thu, May 24, 2018 at 2:08 PM Richard Sandiford <
> richard.sandif...@linaro.org> wrote:
>
>> This patch adds conditional equivalents of the IFN_FMA built-in functions.
>> Most of it is just a mechanical extension of the binary stuff.
>
>> Tested on aarch64-linux-gnu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84413
H.J. Lu changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86469
Matthias Klose changed:
What|Removed |Added
CC||doko at debian dot org
--- Comment #9
1 - 100 of 176 matches
Mail list logo
