The -mupper-regs-{df,di,sf} debug options that I added in previoius versions of
GCC to control whether DFmode, DImode, or SFmode could go in the traditional
Altivec registers has outlived its usefulness. This patch deletes the
options. I fixed up the various tests that used the option, and delete
On 07/21/2017 01:07 PM, Nathan Sidwell wrote:
> [darwin, cygwin, rx maintainers, you might have an opinion]
> Let's at least deprecate it. I attach a patch to do so. With the
> patch, you'll get a note about dbx being deprecated whenever you use
> stabs debugging on a system that prefers stabs (t
On Fri, 2017-07-21 at 19:58 +0200, Volker Reichelt wrote:
> On 21 Jul, David Malcolm wrote:
> > On Thu, 2017-07-20 at 18:35 +0200, Volker Reichelt wrote:
> >> Hi,
> >>
> >> the following patch introduces a new C++ warning option
> >> -Wduplicated-access-specifiers that warns about redundant
> >> a
On Fri, Jul 21, 2017 at 1:58 PM, Andreas Schwab wrote:
> On Jul 21 2017, Ian Lance Taylor wrote:
>
>> In libgo we unconditionally set _FILE_OFFSET_BITS to 64 in
>> configure.ac, so we should unconditionally call the statfs64 and
>> fstatfs64 functions rather than statfs/fstatfs.
>
> That should h
Hi Bill,
On Fri, Jul 21, 2017 at 10:40:43AM -0500, Bill Schmidt wrote:
> In https://gcc.gnu.org/ml/gcc-patches/2017-05/msg00924.html, I raised the
> vectorization cost for a vec_construct operation that requires direct
> moves between GPRs and VSRs. The cost equation I substituted has since
> pro
Ping.
https://gcc.gnu.org/ml/gcc-patches/2017-07/msg00779.html
On Thu, Jul 13, 2017 at 3:00 PM, Jim Wilson wrote:
> The AArch64 port uses SCHED_GROUP to mark instructions that get fused
> at issue time, to ensure that they will be issued together. However,
> in the scheduler, use of a SCHED_GRO
On 7/21/17 4:51 PM, Andrew Pinski wrote:
> So right now how TFmode is handled on AARCH64 not as a pair of 64bit
> registers but rather one 128bit registers (qN registrer; the floating
> point register and the SIMD register set on AARCH64 overlap already).
> So handling TDmode like TFmode is more na
On Fri, Jul 21, 2017 at 2:45 PM, Peter Bergner wrote:
> On 7/13/17 7:12 PM, Andrew Pinski wrote:
>> This patch adds Decimal floating point support to aarch64. It is
>> the base support in that since there is no hardware support for DFP,
>> it just defines the ABI. The ABI I chose is that _Deci
On 7/13/17 7:12 PM, Andrew Pinski wrote:
> This patch adds Decimal floating point support to aarch64. It is
> the base support in that since there is no hardware support for DFP,
> it just defines the ABI. The ABI I chose is that _Decimal32 is
> treated like float, _Decimal64 is treated like do
On Thu, Jul 20, 2017 at 03:56:01PM -0700, Carl Love wrote:
> The following patch is a reworked patch to fix the bugs in the vec_mule
> and vec_mulo patch that had to be reverted. The reverted fix, added the
> correct mule and mulo instructions with vectorization. The
> vectorization support resul
On Jul 21 2017, Ian Lance Taylor wrote:
> In libgo we unconditionally set _FILE_OFFSET_BITS to 64 in
> configure.ac, so we should unconditionally call the statfs64 and
> fstatfs64 functions rather than statfs/fstatfs.
That should happen automatically when building with
_FILE_OFFSET_BITS=64.
>
On Thu, Jul 20, 2017 at 03:56:01PM -0700, Carl Love wrote:
> The following patch is a reworked patch to fix the bugs in the vec_mule
> and vec_mulo patch that had to be reverted. The reverted fix, added the
> correct mule and mulo instructions with vectorization. The
> vectorization support resul
Hi!
DWARF5 introduced DW_AT_export_symbols that may be preset on
DW_TAG_namespace or DW_TAG_{structure,union,class}_type to signalize
inline or anonymous namespaces or anonymous structures/unions/classes.
What we were emitting instead is an implicit DW_TAG_imported_module
in the outer namespace.
On Thu, Jul 20, 2017 at 08:20:52AM -0600, Jeff Law wrote:
> > Can only combine-stack-adjustments do this? It seems like something
> > many passes could do, and then your new note doesn't help.
> SO far it's only been observed with c-s-a, but further auditing is
> certainly desirable here, particul
In libgo we unconditionally set _FILE_OFFSET_BITS to 64 in
configure.ac, so we should unconditionally call the statfs64 and
fstatfs64 functions rather than statfs/fstatfs. These functions
should be available on all versions of GNU/Linux since 2.6. On 64-bit
systems they are aliased to statfs/fsta
> On 21 Jul 2017, at 20:54, Jim Wilson wrote:
>
> On Fri, Jul 21, 2017 at 12:44 PM, Iain Sandoe wrote:
>> It ought to be already, in fact anything (powerpc*/x86/x86-64) >= Darwin9
>> (OS X 10.5) ought to be defaulting to DWARF already, will check that
>> sometime.
>
> Yes, they do default to
On Fri, Jul 21, 2017 at 12:44 PM, Iain Sandoe wrote:
> It ought to be already, in fact anything (powerpc*/x86/x86-64) >= Darwin9 (OS
> X 10.5) ought to be defaulting to DWARF already, will check that sometime.
Yes, they do default to dwarf2. The comments say pre-darwin9 32-bit
defaults to stabs
> On 21 Jul 2017, at 20:10, Mike Stump wrote:
>
> On Jul 21, 2017, at 6:07 AM, Nathan Sidwell wrote:
>>
>> [Darwin, cygwin, rx maintainers, you might have an opinion]
>
> darwin going forward is a DWARF platform, so, shouldn't be a heartache for
> real folks.
agreed,
in fact the default for
On Mon, Jul 17, 2017 at 6:23 AM, Richard Biener
wrote:
> On Mon, Jul 17, 2017 at 8:51 AM, Aldy Hernandez wrote:
>> How does this look?
>
> It's a change that on its own doesn't look worthwhile to me.
>
> So please post the changes that will build ontop of this. Like removing
> anti-ranges from
In the old days there was lookup_fnfields_1 which gave you an index.
Then lazy special function creation hapened and
lookup_fnfields_idx_nolazy appeared. Then users wanted the overloads
directly so lookup_fnfields_slot and lookup_fnfields_slot_nolazy were born.
Now everybody uses the slot acc
This patch makes some changes to the way the PowerPC handles IEEE 128-bit
floating point, and I wanted to point out where I would like to change the
compiler, but be open to doing it in other ways.
There are 3 changes in this patch, and presumably more work to do beyond this
patch.
The first chan
On Jul 21, 2017, at 9:03 AM, Jim Wilson wrote:
> There is also the matter of SDB_DEBUG which is still supported, and is
> no longer used by anyone, as we have already deprecated all of the
> COFF targets that were using it. SDB support for C++ is even worse
> than the DBX support. This should be
On Jul 21, 2017, at 6:07 AM, Nathan Sidwell wrote:
>
> [darwin, cygwin, rx maintainers, you might have an opinion]
darwin going forward is a DWARF platform, so, shouldn't be a heartache for real
folks. For ancient machines, ancient compilers might be a requirement.
Generally, I like keeping
If getSiginfo in libgo does not know how to determine the PC, it will
call runtime_callers. That can happen in a thread that was started by
non-Go code, in which case the TLS variable g will not be set, in
which case runtime_lock will crash.
Avoid the problem by using atomic operations for the loc
Hi,
Due to the way bit-field access lower is done, we can get an
unitialized memory load and this causes the unitialized warning to
kick in.
The case we have is:
temp_1 = BIT_FIELD_REF
temp_2 = BIT_INSERT
BIT_FIELD_REF = temp_2
What this patch does is similar to what was done for the case of
BIT
Jeff Law wrote:
> Examples please? We should be probing the outgoing args at the probe
> interval once the total static frame is greater than 3k. The dynamic
> space should be probed by generic code.
OK, here are a few simple examples that enable a successful jump of the stack
guard despit
ctors and dtors had special slots in the METHOD_VEC, because they used
not to have proper names. Now they have unique identifiers, we can
treat them just as any other function and look them up by
[cd]tor_identifier.
(the eventual goal is to replace separate METHOD_VEC and FIELD_VEC with
a si
This patch to libgo changes the signal handler for PPC (and PPC64)
GNU/Linux to fetch the PC from the signal context. Bootstrapped and
ran Go testsuite on x86_64-pc-linux-gnu and
powerpc64le-unknown-linux-gnu. Committed to mainline.
Ian
Index: gcc/go/gofrontend/MERGE
On Mon, May 15, 2017 at 7:24 AM, REIX, Tony wrote:
> Description:
> * This patch enables libbacktrace to handle XCOFF on AIX.
>
> Tests:
> * Fedora25/x86_64 + GCC v7.1.0 : Configure/Build: SUCCESS
>- build made by means of a .spec file based on Fedora gcc-7.0.1-0.12 .spec
> file
> ../confi
I wandered into add_candidates and got confused by !!. There were a few
opportunities for other cleanup too, so committed the attached.
nathan
--
Nathan Sidwell
2017-07-21 Nathan Sidwell
* call.c (add_candidates): Move decls to initialization. Don't
use !!.
Index: call.c
===
On 21 Jul, David Malcolm wrote:
> On Thu, 2017-07-20 at 18:35 +0200, Volker Reichelt wrote:
>> Hi,
>>
>> the following patch introduces a new C++ warning option
>> -Wduplicated-access-specifiers that warns about redundant
>> access-specifiers in classes, e.g.
>>
>> class B
>> {
>> public:
This libgo patch tweaks the CgoCallbackGC test to allocate more stack
space. This makes it more likely to succeed on a system that does not
support split stacks. This test is actually not very meaningful for
gccgo at present, but it doesn't hurt to keep running it.
Bootstrapped and ran Go tests o
This is a ping for my patch to enable the ifunc resolver by default for
aarch64.
https://gcc.gnu.org/ml/gcc-patches/2017-06/msg00806.html
Steve Ellcey
sell...@cavium.com
On 07/20/2017 10:35 AM, Volker Reichelt wrote:
Hi,
the following patch introduces a new C++ warning option
-Wduplicated-access-specifiers that warns about redundant
access-specifiers in classes, e.g.
class B
{
public:
B();
private:
void foo();
private:
int i;
Hi Richard,
I would like to backport this fix to GCC 5, 6, and 7. All have passed regstrap
on
powerpc64le-linux-gnu (with the test case moved to gcc.dg/ubsan, of course).
Is this ok?
Thanks!
-- Bill
> On Jul 14, 2017, at 1:05 PM, Bill Schmidt wrote:
>
> Hi,
>
> PR81162 identifies a bug in
On 07/20/2017 07:23 AM, Segher Boessenkool wrote:
> Hi Jeff,
>
> On Tue, Jul 18, 2017 at 11:17:19PM -0600, Jeff Law wrote:
>>
>> The biggest change in this update to patch 01/08 is moving of stack
>> clash protection out of -fstack-check= and into its own option,
>> -fstack-clash-protection. I be
On 21 Jul, David Malcolm wrote:
> On Fri, 2017-07-21 at 11:56 -0400, David Malcolm wrote:
>> On Thu, 2017-07-20 at 18:35 +0200, Volker Reichelt wrote:
>> > Hi,
>> >
>> > the following patch introduces a new C++ warning option
>> > -Wduplicated-access-specifiers that warns about redundant
>> > acce
On Wed, Jul 19, 2017 at 11:13 AM, Richard Biener
wrote:
> On July 19, 2017 6:10:28 PM GMT+02:00, Andrew Pinski
> wrote:
>>On Mon, Jul 17, 2017 at 3:02 AM, Richard Biener
>> wrote:
>>> On Thu, Jul 13, 2017 at 6:18 AM, Andrew Pinski
>>wrote:
On Wed, Jul 12, 2017 at 9:10 PM, Marc Glisse
>>wr
On 07/21/2017 07:23 AM, Andreas Krebbel wrote:
> Hi,
>
> I've used your patch as the base and applied my changes on top. The
> attached patch is the result, so it is supposed to replace your
> version. It now also supports emitting a runtime loop.
Thanks a ton! I'll roll your changes into the V
Hi
Here is a proposal for 2 optimizations in the std::list implementation.
Optimization on the move constructor taking an allocator for always
equal allocators. Compare to the version in my previous std::list patch
I am now doing it at std::list level rather than at _List_base level.
On Fri, 2017-07-21 at 11:56 -0400, David Malcolm wrote:
> On Thu, 2017-07-20 at 18:35 +0200, Volker Reichelt wrote:
> > Hi,
> >
> > the following patch introduces a new C++ warning option
> > -Wduplicated-access-specifiers that warns about redundant
> > access-specifiers in classes, e.g.
> >
> >
On Thu, Apr 27, 2017 at 05:08:38AM +, Hurugalawadi, Naveen wrote:
> Hi,
>
> The instruction "vec_pack_trunc_" should be split after register
> allocator for scheduling reasons. Currently the instruction is marked as type
> multiple which means it will scheduled as single issued. However, nothi
On Fri, 2017-07-14 at 15:38 +0200, Marek Polacek wrote:
> I think David might be able to approve this one, so CCing.
It's something of a stretch for my "diagnostic messages" maintainer
hat, but I've looked over these changes and they look good to me.
Dave
> On Tue, Jul 11, 2017 at 03:23:16PM +02
Use the BUILD_PATH_PREFIX_MAP environment variable when expanding the __FILE__
macro, in the same way that debug-prefix-map works for debugging symbol paths.
This patch follows similar lines to the earlier patch for SOURCE_DATE_EPOCH.
Specifically, we read the environment variable not in libcpp bu
Define the BUILD_PATH_PREFIX_MAP environment variable, and treat it as implicit
-fdebug-prefix-map CLI options specified before any explicit such options.
Much of the generic code for applying and parsing prefix-maps is implemented in
libiberty instead of the dwarf2 parts of the code, in order to
Change the remapping algorithm so that each old_prefix only matches paths that
have old_prefix as a whole path component prefix. (A whole path component is a
part of a path that begins and ends at a directory separator or at either end
of the path string.)
This remapping algorithm is more predict
(Please keep me on CC, I am not subscribed)
Proposal
This patch series adds a new environment variable BUILD_PATH_PREFIX_MAP. When
this is set, GCC will treat this as extra implicit "-fdebug-prefix-map=$value"
command-line arguments that precede any explicit ones. This makes the final
b
On 05/07/17 21:24 +0100, Jonathan Wakely wrote:
On 05/07/17 20:44 +0100, Yuri Gribov wrote:
On Wed, Jul 5, 2017 at 8:00 PM, Jonathan Wakely wrote:
This patch adds AddressSanitizer annotations to std::vector, so that
ASan can detect out-of-bounds accesses to the unused capacity of a
vector. e.g
On Fri, Jul 21, 2017 at 7:15 AM, David Edelsohn wrote:
> AIX still uses DBX as the primary debugging format. AIX supports
> DWARF but the AIX toolchain does not fully interoperate with DWARF
> generated by GCC.
We could still deprecate DBX_DEBUG while leaving XCOFF_DEBUG alone for
now. This wou
On Thu, 2017-07-20 at 18:35 +0200, Volker Reichelt wrote:
> Hi,
>
> the following patch introduces a new C++ warning option
> -Wduplicated-access-specifiers that warns about redundant
> access-specifiers in classes, e.g.
>
> class B
> {
> public:
> B();
>
> private:
> voi
Previous revision here: https://gcc.gnu.org/ml/gcc-patches/2017-07/msg01090.html
Reassociate X * CST1 * CST2 to X * (CST1 * CST2).
Changed in this revision:
- remove the check for @2 being 0 or -1
* match.pd ((X * CST1) * CST2): Simplify to X * (CST1 * CST2).
testsuite:
* gcc.dg/
Previous revision here: https://gcc.gnu.org/ml/gcc-patches/2017-07/msg00889.html
Reassociate (X * CST) * Y to (X * Y) * CST, this pushes constants in
multiplication chains to outermost factors, where they can be combined.
Changed in this revision:
- remove !TYPE_OVERFLOW_SANITIZED and !TYPE_SATUR
On 21.07.2017 13:41, Richard Biener wrote:
On Thu, Jul 20, 2017 at 3:18 PM, Georg-Johann Lay wrote:
Hi, this patch fixes some minor problems in lto-plugin:
Some older mingw32 host environments have broken asprintf.
As far as I can tell, the problem is that the mingw asprintf
implementation cal
Hi,
In https://gcc.gnu.org/ml/gcc-patches/2017-05/msg00924.html, I raised the
vectorization cost for a vec_construct operation that requires direct
moves between GPRs and VSRs. The cost equation I substituted has since
proven to be slightly more conservative than attended, and we're seeing
some c
On 29/06/17 21:53, Jim Wilson wrote:
> Falkor is an ARMV8-A part, but also includes the RDMA extension from
> ARMV8.1-A.
> I'd like to enable support for the RDMA instructions when -mcpu=falkor is
> used,
> and also make the RDMA intrisics available. To do that, I need to add rdma
> as an archit
Hello,
The final tie-breaker in pair_cmp comparator looks strange, it correctly
yields zero for equal expr->symtree-n.sym values, but for unequal values
it produces 0 or 1. This would be correct for C++ STL-style comparators
that require "less-than" predicate to be computed, but not for C qsort.
> Nathan Sidwell writes:
> Let's at least deprecate it. I attach a patch to do so. With the
> patch, you'll get a note about dbx being deprecated whenever you use
> stabs debugging on a system that prefers stabs (thus both -g and -gstabs
> will warn). On systems where stabs is not preferred
On 07/21/2017 09:16 AM, Richard Biener wrote:
On Fri, Jul 21, 2017 at 3:07 PM, Nathan Sidwell wrote:
+#ifndef DBX_DEBBUG_OK
^^^
typo? The patch doesn't define this anywhere - I suggest to add it to
defaults.h
as 0 and use #if? Also would need documenting if this is
On 07/21/2017 11:41 AM, Richard Biener wrote:
On Thu, 20 Jul 2017, Tom de Vries wrote:
On 07/20/2017 12:10 PM, Richard Biener wrote:
On Thu, 20 Jul 2017, Tom de Vries wrote:
Hi,
this patch fixes PR81430, an ICE in the libgomp testsuite for both openmp
and
openacc test-cases for x86_64 with
Hi,
I've used your patch as the base and applied my changes on top. The
attached patch is the result, so it is supposed to replace your
version. It now also supports emitting a runtime loop.
It bootstraps fine but unfortunately I see an Ada regression which I
haven't tracked down yet.
> FAIL:
On 13/07/17 11:26, Michael Collison wrote:
> Updated per Richard's comments and suggestions.
>
> Okay for trunk?
OK. Please can you write up an entry for the release notes (wwwdocs).
R.
>
> 2017-07-10 Michael Collison
>
> * config/arm/arm.c (arm_option_override): Deprecate
> u
On Fri, Jul 21, 2017 at 3:07 PM, Nathan Sidwell wrote:
> [darwin, cygwin, rx maintainers, you might have an opinion]
>
> On 07/21/2017 01:11 AM, Richard Biener wrote:
>>
>> On July 21, 2017 12:03:58 AM GMT+02:00, Jim Wilson
>> wrote:
>>>
>>> On Thu, Jul 20, 2017 at 2:00 PM, Nathan Sidwell wrote:
On Fri, Jul 21, 2017 at 1:38 AM, 吴潍浠(此彼) wrote:
> Hi Jeff
>
> I have signed the copyright assignment, and used the name 'Wish Wu' .
> Should I send you a copy of my assignment ?
Your assignment now is on file in the FSF Copyright Assignment list
where Jeff, I and other maintainers can see it. We
When forcing versioning for the vector profitability check I noticed
we use different niters for the peeling check than for the versioning one
leading to two branches, the 2nd being redundant. The following makes
that consistent, also using the known not overflown number of latch
execution count.
[darwin, cygwin, rx maintainers, you might have an opinion]
On 07/21/2017 01:11 AM, Richard Biener wrote:
On July 21, 2017 12:03:58 AM GMT+02:00, Jim Wilson
wrote:
On Thu, Jul 20, 2017 at 2:00 PM, Nathan Sidwell wrote:
With this patch the gdb stabs test results are still awful, but they
ar
Hi!
This patch adds an Implementing-TASKLOOP-construct section as well as a
description for GOMP_doacross_ runtime routines family to
Implementing-FOR-Construct section. (I checked that 'make info' and 'make html'
produce correct doc output)
2017-07-21 Igor Venevtsev
* libgomp.texi
Hi all,
This merges vector multiplies and adds into a single mla instruction
when the multiplication is done by a scalar.
Currently, for the following:
typedef int __attribute__((vector_size(16))) vec;
vec
mla0(vec v0, vec v1, vec v2)
{
return v0 + v1 * v2[0];
}
On Thu, Jul 20, 2017 at 3:18 PM, Georg-Johann Lay wrote:
> Hi, this patch fixes some minor problems in lto-plugin:
>
> Some older mingw32 host environments have broken asprintf.
> As far as I can tell, the problem is that the mingw asprintf
> implementation calls _vsnprintf (NULL, 0, ...) which al
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied.
Richard.
2017-06-21 Richard Biener
PR tree-optimization/81500
* tree-vect-loop.c (vect_is_simple_reduction): Properly fail if
we didn't identify a reduction path.
* gcc.dg/torture/pr81500.c: New te
ping
Wilco Dijkstra wrote:
> James Greenhalgh wrote:
>
> > I note this is still marked as an RFC, are you now proposing it as a
> > patch to be merged to trunk?
>
> Absolutely. It was marked as an RFC to get some comments - I thought it
> may be controversial to separate the frame po
ping
From: Wilco Dijkstra
Sent: 17 January 2017 15:14
To: Richard Earnshaw; GCC Patches; James Greenhalgh
Cc: nd
Subject: Re: [PATCH v3][AArch64] Fix symbol offset limit
Here is v3 of the patch - tree_fits_uhwi_p was necessary to ensure the size of a
declaration is an integer. So the qu
ping
This patch further improves aarch64_legitimate_constant_p. Allow all
integer, floating point and vector constants. Allow label references
and non-anchor symbols with an immediate offset. This allows such
constants to be rematerialized, resulting in smaller code and fewer stack
sp
ping
As described in PR79041, -mcmodel=large -mpc-relative-literal-loads
may be used to avoid generating ADRP/ADD or ADRP/LDR. However both
trunk and GCC7 may still emit ADRP for some constant pool literals.
Fix this by adding a aarch64_pcrelative_literal_loads check.
OK for trunk/GCC
Ping ?
Thanks,
Kugan
On 27 June 2017 at 11:20, Kugan Vivekanandarajah
wrote:
> https://gcc.gnu.org/ml/gcc-patches/2016-03/msg00614.html added this
> workaround to get kernel building with when TARGET_FIX_ERR_A53_843419
> is enabled.
>
> This was added to support building kernel loadable modules
Hi,
this patch adds nvptx_override_options_after_change, containing a
workaround for PR81430.
Tested on x86_64 with nvptx accelerator.
Committed.
Thanks,
- Tom
Add nvptx_override_options_after_change
2017-07-21 Tom de Vries
PR lto/81430
* config/nvptx/nvptx.c (nvptx_override_options_a
On Thu, 20 Jul 2017, Tom de Vries wrote:
> On 07/20/2017 12:10 PM, Richard Biener wrote:
> > On Thu, 20 Jul 2017, Tom de Vries wrote:
> >
> > > Hi,
> > >
> > > this patch fixes PR81430, an ICE in the libgomp testsuite for both openmp
> > > and
> > > openacc test-cases for x86_64 with nvptx accel
On 07/20/2017 03:04 PM, Tom de Vries wrote:
On 07/13/2017 06:53 PM, Cesar Philippidis wrote:
Similarly, for nvptx vector reductions, when it comes time to initialize
the reduction variable, the nvptx BE constructs a branch so that only
vector lanes 1 to vector_length-1 are initialized the the de
On Fri, 21 Jul 2017, Bin.Cheng wrote:
> On Fri, Jul 21, 2017 at 8:12 AM, Richard Biener wrote:
> >
> > The following is sth I noticed when looking at a way to fix PR81303.
> > We happily compute a runtime cost model threshold that executes the
> > vectorized variant even though no vector iteratio
This fixes mismatched cost compute in peeling cost estimation by
using the same routine also for no peeling costing (the original
implementation failed to handle the same special cases such as
groups and thus always over-estimated no peeling cost...).
It doesn't disable peeling for bwaves for me
On Fri, Jul 21, 2017 at 10:36:46AM +0200, Ulrich Drepper wrote:
> While looking through dwarf2out.c I came across this if expression where
> supposedly in case DWARF before 5 is used the 128 LEB encoding is used.
> This of course cannot be the case. There isn't really a deeper problem
> since th
While looking through dwarf2out.c I came across this if expression where
supposedly in case DWARF before 5 is used the 128 LEB encoding is used.
This of course cannot be the case. There isn't really a deeper problem
since the entire block is guarded by a test for at least DWARF 5.
I propose the
Hi Honza,
Just a couple of typo nits.
Cheers,
Kyrill
On 21/07/17 00:38, Jan Hubicka wrote:
Hello,
Caroline disabled crossjumping with bb-reordering in initial patch implementing
this pass. According to discussion with Rth it was only becuase she was unsure
how to prevent crossjumping to mix u
On Fri, Jul 21, 2017 at 8:12 AM, Richard Biener wrote:
>
> The following is sth I noticed when looking at a way to fix PR81303.
> We happily compute a runtime cost model threshold that executes the
> vectorized variant even though no vector iteration takes place due
> to the number of prologue/epi
The following is sth I noticed when looking at a way to fix PR81303.
We happily compute a runtime cost model threshold that executes the
vectorized variant even though no vector iteration takes place due
to the number of prologue/epilogue iterations. The following fixes
that -- note that if we do
84 matches
Mail list logo
