On Sun, Jul 15, 2018 at 11:21:56PM +0200, Tom de Vries wrote:
> 2018-07-15 Tom de Vries
>
> * var-tracking.c (vt_initialize): Fix pre_dec handling. Print adjusted
> insn slim if dump_flags request TDF_SLIM.
>
> * gcc.target/i386/vartrack-1.c: New test.
>
> ---
> --- a/gcc/v
On Fri, 13 Jul 2018, Sandra Loosemore wrote:
> On 07/03/2018 07:55 AM, Richard Biener wrote:
> >
> > Bootstrapped and tested on x86_64-unknown-linux-gnu, applied.
> >
> > Richard.
> >
> > From 52aad98947e5cfcb5624ff24f0c557d0029c34fe Mon Sep 17 00:00:00 2001
> > From: Richard Guenther
> > Dat
This is the counterpart of the i386 feature introduced by
39a5a6a4: Add direct support for Linux kernel __fentry__ patching.
This is the counterpart of the i386 feature introduced by
39a5a6a4: Add direct support for Linux kernel __fentry__ patching.
* gcc/config/s390/s390.c (s390_function_profiler): Generate
__mcount_loc section.
* gcc/config/s390/s390.opt: Add the new option.
* gcc/tests
This is the counterpart of the i386 feature introduced by
39a5a6a4: Add direct support for Linux kernel __fentry__ patching.
On i386 the profiler call sequence always consists of 1 call
instruction, so -mnop-mcount generates a single nop with the same
length as a call. For S/390 longer sequences m
This is the counterpart of the i386 feature introduced by
39a5a6a4: Add direct support for Linux kernel __fentry__ patching.
On i386, the difference between mcount and fentry is that fentry
comes before the prolog. On s390 mcount already comes before the
prolog, but takes 4 instructions. This patc
Hi,
this is a regression present on the mainline and 8 branch in the form of wrong
code generated for an Ada program manipulating bit-packed boolean array types.
The problem is in the new range optimization code of the reassoc pass: from
_64 = _63 | 4;
_73 = _64 & 191;
_76 = _64 >> 6;
_
On 07/13/2018 04:58 PM, Andreas Schwab wrote:
> On Jul 13 2018, Andreas Krebbel wrote:
>
>> @@ -5645,3 +5657,5 @@ OBJECT:8:_ZTTSi@@GLIBCXX_3.4
>> OBJECT:8:_ZTTSo@@GLIBCXX_3.4
>> OBJECT:8:_ZTTSt13basic_istreamIwSt11char_traitsIwEE@@GLIBCXX_3.4
>> OBJECT:8:_ZTTSt13basic_ostreamIwSt11char_traitsI
Hi Thomas,
>> I tested it on a fairly large code base and found no further false
>> positives. Also it still regtests cleanly. Ok for trunk?
>
>
> while I still disagree with this on principle, I will not stand
> in the way.
IIUC you disagree in the sense that you would like gfortran to have
more
On Mon, Jul 16, 2018 at 9:52 AM Eric Botcazou wrote:
>
> Hi,
>
> this is a regression present on the mainline and 8 branch in the form of wrong
> code generated for an Ada program manipulating bit-packed boolean array types.
>
> The problem is in the new range optimization code of the reassoc pass
On Fri, Jul 13, 2018 at 5:40 PM Uros Bizjak wrote:
>
> As demonstrated in the PR, middle-end changes the trappines of the
> compare by expanding non-trapping compare to a combination of
> setcc/cmove branchless code, e.g. UNLT is split to UNORDERED setcc and
> LT cmove.
>
> The above conversion is
gcc/ChangeLog:
2018-07-11 Martin Liska
* align.h (MAX_CODE_ALIGN): New.
(MAX_CODE_ALIGN_VALUE): New.
* common/config/i386/i386-common.c (ix86_handle_option):
(MAX_CODE_ALIGN): Moved to align.h.
* final.c (MAX_CODE_ALIGN): Likewise.
* opts.c (par
gcc/ChangeLog:
2018-07-11 Martin Liska
* config/i386/att.h (ASM_OUTPUT_ALIGN): Fix spacing
in order to fulfil coding style.
* config/i386/cygming.h (ASM_OUTPUT_ALIGN): Likewise.
* config/i386/gas.h (ASM_OUTPUT_MAX_SKIP_ALIGN): Likewise.
* config/i386/x8
gcc/ChangeLog:
2018-07-11 Martin Liska
* align.h: New file.
* config/alpha/alpha.c (alpha_align_insns_1): Use align_functions
directly.
* config/i386/i386.c (ix86_avoid_jump_mispredicts): Use new return type
align_flags of label_to_alignment.
* config/
gcc/ChangeLog:
2018-07-12 Martin Liska
* opts.c: Do not enable OPT_falign_* for -Os.
---
gcc/opts.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/gcc/opts.c b/gcc/opts.c
index 0625b15b27b..b8ae8756b4f 100644
--- a/gcc/opts.c
+++ b/gcc/opts.c
@@ -510,10 +
Hi.
As you probably noticed, current trunk accepts extended format
of -falign-FOO options.
However there are some limitations that are addressed in the patchset:
1) E.g. align_labels_max_skip and align_labels_log are separate
values and targets can override them via LABEL_ALIGN and
LABEL_AL
On Mon, Jul 16, 2018 at 09:24:10AM +0200, Jakub Jelinek wrote:
> On Sun, Jul 15, 2018 at 11:21:56PM +0200, Tom de Vries wrote:
> > 2018-07-15 Tom de Vries
> >
> > * var-tracking.c (vt_initialize): Fix pre_dec handling. Print adjusted
> > insn slim if dump_flags request TDF_SLIM.
> >
>
> Thanks. In that light the unsharing at the places the FE builds expressions
> using TYPE_SIZE and friends looks like the way to go.
Probably, yes.
> I still wonder why unsharing in gimplify_one_sizepos is necessary though.
> Ist that because even deep unsharing doesn't walk types?
walk_tree wa
On Mon, 16 Jul 2018, Eric Botcazou wrote:
> > Thanks. In that light the unsharing at the places the FE builds expressions
> > using TYPE_SIZE and friends looks like the way to go.
>
> Probably, yes.
OK, let's see what C family maintainers decide on ultimatively.
> > I still wonder why unsharing
Hi,
This is a rewrite of the tag collision avoidance patch that Kugan had
written as a machine reorg pass back in February.
The falkor hardware prefetching system uses a combination of the
source, destination and offset to decide which prefetcher unit to
train with the load. This is great when l
Committed,
Claudiu
From: Andrew Burgess [andrew.burg...@embecosm.com]
Sent: Saturday, July 07, 2018 12:21 AM
To: Claudiu Zissulescu
Cc: gcc-patches@gcc.gnu.org; francois.bed...@synopsys.com; Claudiu Zissulescu
Subject: Re: [PATCH] [ARC] Add support for HS4x
Hi Sam
On 13/07/18 17:09, Sam Tebbs wrote:
Hi all,
This patch adds an optimisation that exploits the AArch64 BFXIL instruction
when or-ing the result of two bitwise and operations with non-overlapping
bitmasks (e.g. (a & 0x) | (b & 0x)).
Example:
unsigned long long combine(uns
> But on zEC12 LA works pretty much the same as on z13/z14, it is
> indeed not cracked, but still a 2-cycle instruction when using
> an index register. So I guess the change really should apply
> to zEC12 as well, and this could be as simple as changing the
> above line to:
>
> if (addr.indx &&
> Le 15 juil. 2018 à 21:35, Rainer Orth a écrit
> :
>
> Hi Jerry,
>
>> On 07/15/2018 11:46 AM, Rainer Orth wrote:
>>> Hi Jerry,
>>>
Hmm, interesting. Which linux are you using?
>>>
>>> Fedora 27.
>>
>> Works for me. Fedora 28. Do not know for other OS's
>
> just tried Solaris 11/x86
Hi,
over the last weeks, while working on various diagnostic issues, I
noticed a few defective permerror + inform pairs. Tested x86_64-linux.
Thanks, Paolo.
/cp
2018-07-16 Paolo Carlini
* class.c (resolve_address_of_overloaded_function): Don't emit an
From: claziss
gcc/
2017-06-14 Claudiu Zissulescu
* config/arc/arc.h (ADDITIONAL_REGISTER_NAMES): Add additional
register names.
---
gcc/config/arc/arc.h | 10 +-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/gcc/config/arc/arc.h b/gcc/config/arc/arc.h
i
Improve selection of short instruction for fp-moves.
gcc/
2018-05-17 Claudiu Zissulescu
* config/arc/arc.md (movsf_insn): Add short instruction selection.
* config/arc/constraints.md (CfZ): New constraint.
* config/arc/fpu.md (addssf3_fpu): Use CfZ constraint.
(
gcc/
2018-05-09 Claudiu Zissulescu
* config/arc/arc.c (compact_memory_operand_p): Check for uncached
accesses as well.
(arc_is_uncached_mem_p): uncached applies to both the variable and
the pointer.
testsuite/
2018-05-09 Claudiu Zissulescu
* gcc.targ
Update the list of default optimizations used for size compilations.
gcc/
2018-07-10 Claudiu Zissulescu
* common/config/arc/arc-common.c (arc_option_optimization_table):
Update default optimizations for size.
---
gcc/common/config/arc/arc-common.c | 13 +
1 file ch
Howdy!
I've abstracted out the cross product calculations into its own
function, and have adapted it to deal with wide ints so it's more
reusable. It required some shuffling around, and implementing things a
bit different, but things should be behave as before.
I also renamed vrp_int_const_
Hi,
this is an idea that I'm currently playing around with: adding nops in
an optimized application with debug info can improve the debug info.
Consider f.i. this gdb session in foo of pr54200-2.c (using -Os):
...
(gdb) n
26return a; /* { dg-final { gdb-test . "(int)a" "6" } } */
(gd
Hi.
This is one more revert related to symbol_summary.
Patch can bootstrap on ppc64le-redhat-linux and survives regression tests.
I'm going to install the patch.
Martin
gcc/ChangeLog:
2018-07-16 Martin Liska
PR ipa/86529
* ipa-pure-const.c (malloc_candidate_p): Revert ::get
On Mon, Jul 16, 2018 at 03:29:10PM +0200, Tom de Vries wrote:
> this is an idea that I'm currently playing around with: adding nops in
> an optimized application with debug info can improve the debug info.
>
> Consider f.i. this gdb session in foo of pr54200-2.c (using -Os):
> ...
> (gdb) n
> 26
On 07/16/2018 01:02 PM, Robin Dapp wrote:
>> But on zEC12 LA works pretty much the same as on z13/z14, it is
>> indeed not cracked, but still a 2-cycle instruction when using
>> an index register. So I guess the change really should apply
>> to zEC12 as well, and this could be as simple as changin
On Mon, 16 Jul 2018, Tom de Vries wrote:
> Hi,
>
> this is an idea that I'm currently playing around with: adding nops in
> an optimized application with debug info can improve the debug info.
>
>
> Consider f.i. this gdb session in foo of pr54200-2.c (using -Os):
> ...
> (gdb) n
> 26
The 07/13/2018 17:46, Jeff Law wrote:
> On 07/12/2018 11:39 AM, Tamar Christina wrote:
> >>> +
> >>> + /* Round size to the nearest multiple of guard_size, and calculate the
> >>> + residual as the difference between the original size and the rounded
> >>> + size. */
> >>> + HOST_WIDE_INT
The following fixes PR86523, we failed to assing DIE parents to some
function-local entities with the idea scope vars would pick them up
but that's not true for some of them.
Bootstrapped and tested on x86_64-unknown-linux-gnu, LTO bootstrapped
on the GCC 8 branch (it's said LTO bootstrap is bro
On Mon, Jul 16, 2018 at 10:54 AM marxin wrote:
>
> Hi.
>
> As you probably noticed, current trunk accepts extended format
> of -falign-FOO options.
> However there are some limitations that are addressed in the patchset:
>
> 1) E.g. align_labels_max_skip and align_labels_log are separate
>valu
This will reduce significantly the number of allocations done when
doing consecutive append operations.
Tested on x86_64-pc-linux-gnu, committed on trunk
2018-07-16 Nicolas Roche
gcc/ada/
* libgnat/a-strunb.adb, libgnat/a-strunb__shared.adb: Adjust growth
factor from 1/32 to
This patch prevents the compiler from entering infinite recursion when
processing an illegal deferred constant.
-- Source --
-- types.ads
package Types is
type Enum is (One, Two);
end Types;
-- types2.ads
with Types;
package Types2 is
type Enum is private;
The compiler fails to generate a call to detect allocators executed after
elaboration in cases where the allocator is associated with Global_Pool_Object.
The fix is to test for this associated storage pool as part of the condition
for generating a call to System.Elaboration_Allocators.Check_Standar
The frontend generates special functions for checking subtype predicates,
type invariants and Default_Initial_Condition aspect. These are translated
as predicates in GNATprove, and as such should no call inside these
functions should be inlined. This is similar to the existing handling of
calls ins
This patch allows the compiler to report an error on Bit_Order when
defined for a record extension.
Tested on x86_64-pc-linux-gnu, committed on trunk
2018-07-16 Javier Miranda
gcc/ada/
* sem_ch13.adb (Analyze_Attribute_Definition_Clause): Report an error
on Bit_Order when def
Processing sources under -gnatd.F the frontend may crash on
an iterator of the form 'for X of ...' over an array if the
iterator is located in an inlined subprogram.
Tested on x86_64-pc-linux-gnu, committed on trunk
2018-07-16 Javier Miranda
gcc/ada/
* exp_ch5.adb (Expand_Iterator_Lo
This patch updates the routines which produce Wide_String and Wide_Wide_String
from a String to construct a result of the proper maximum size which is later
sliced.
Tested on x86_64-pc-linux-gnu, committed on trunk
2018-07-16 Hristian Kirtchev
gcc/ada/
* libgnat/s-wchwts.adb (Wide_St
This patch is preventive: it improves checks on inline functions that
return unconstrained type. It does not change the functionality of
the compiler.
Tested on x86_64-pc-linux-gnu, committed on trunk
2018-07-16 Javier Miranda
gcc/ada/
* inline.adb (Build_Body_To_Inline): Minor code
This patch corrects an issue whereby spurious unhandled exception warnings on
integer literals within static if and case expressions would be emitted when
the restriction No_Exception_Propagation is enabled.
-- Source --
-- gnat.adc
pragma Restrictions (No_Exception_Pr
This patch corrects the generation of helper functions which verify the
validity of record type scalar discriminants and scalar components when
switches -gnata (assertions enabled) and -gnateV (validity checks on
subprogram parameters) are in effect.
Tested on x86_64-pc-linux-gnu, committed on tru
We previously removed the calls to Set_Withed_Body; this commit deconstructs
calls to Withed_Body, which always returned False.
The Set_Withed_Body/Withed_Body were helping the Walk_Library_Items routine
traverse the AST of several compilation units such that declarations are
visited before refere
This patch corrects the mechanism which ensures that a package with a null
Abstract_State does not introduce hidden state, by ignoring internal states
and variables because they do not represent the "source" hidden state.
Tested on x86_64-pc-linux-gnu, committed on trunk
2018-07-16 Hristian Kirt
The debug switch -gnatd.WW enables extra info when traversing library units
with Walk_Library_Items, which is used in the CodePeer and GNATprove. This
routine was crashing when trying to print info about a unit with configuration
pragmas (typically an .adc file). Now fixed.
No test, as the crash o
The Withed_Body field was added to N_With_Clause node to help the
Walk_Library_Items routine, which was created for the CodePeer backend
and later adopted by the GNATprove.
This routine is meant to traverse all library units, such that declarations
are visited before references. However, for compl
This patch modifies the analysis of package contracts to split processing
which is specific to package instantiations on its own. As a result, the
lack of indicator Part_Of can now be properly assessed.
-- Source --
-- gen_pack.ads
generic
package Gen_Pack is
Pack_V
On 07/16/2018 03:34 PM, Jakub Jelinek wrote:
> On Mon, Jul 16, 2018 at 03:29:10PM +0200, Tom de Vries wrote:
>> this is an idea that I'm currently playing around with: adding nops in
>> an optimized application with debug info can improve the debug info.
>>
>> Consider f.i. this gdb session in foo
On 07/16/2018 09:48 AM, Ilya Leoshkevich wrote:
> This is the counterpart of the i386 feature introduced by
> 39a5a6a4: Add direct support for Linux kernel __fentry__ patching.
>
> On i386, the difference between mcount and fentry is that fentry
> comes before the prolog. On s390 mcount already co
On 07/16/2018 09:48 AM, Ilya Leoshkevich wrote:
> This is the counterpart of the i386 feature introduced by
> 39a5a6a4: Add direct support for Linux kernel __fentry__ patching.
>
> * gcc/config/s390/s390.c (s390_function_profiler): Generate
> __mcount_loc section.
> * gcc/c
On 07/16/2018 09:48 AM, Ilya Leoshkevich wrote:
> This is the counterpart of the i386 feature introduced by
> 39a5a6a4: Add direct support for Linux kernel __fentry__ patching.
>
> On i386 the profiler call sequence always consists of 1 call
> instruction, so -mnop-mcount generates a single nop wi
On 16/07/18 09:58 +0200, Andreas Krebbel wrote:
On 07/13/2018 04:58 PM, Andreas Schwab wrote:
On Jul 13 2018, Andreas Krebbel wrote:
@@ -5645,3 +5657,5 @@ OBJECT:8:_ZTTSi@@GLIBCXX_3.4
OBJECT:8:_ZTTSo@@GLIBCXX_3.4
OBJECT:8:_ZTTSt13basic_istreamIwSt11char_traitsIwEE@@GLIBCXX_3.4
OBJECT:8:_ZT
On 07/16/2018 03:50 PM, Richard Biener wrote:
> On Mon, 16 Jul 2018, Tom de Vries wrote:
>
>> Hi,
>>
>> this is an idea that I'm currently playing around with: adding nops in
>> an optimized application with debug info can improve the debug info.
>>
>>
>> Consider f.i. this gdb session in foo of p
Hi,
this fixes PR middle-end/86528.
Bootstrapped and reg-tested on x86_64-pc-linux-gnu.
Is it OK for trunk?
Thanks
Bernd.
gcc:
2018-07-04 Bernd Edlinger
PR middle-end/86528
* builtins.c (check_access): Bail out if range[0] is no INTEGER_CST.
* expr.c (string_constant): Fix the element s
Hi,
Would you be interested in Bentley Systems Users List for your sales and
marketing campaigns?
We can provide you Database from North America, Latin America, EMEA, and
APAC.
Information Fields – Name, Title, Email, Phone Numbers, Company Name, and
Company Details like Physical Addres
Rebased and update patch (typos, add missing annotations),
add ASan teststo verify string annotation.
On 06/28/2018 11:09 AM, Mikhail Kashkarov wrote:
> ^ gentle ping.
>
>
> On 06/08/2018 05:54 PM, Mikhail Kashkarov wrote:
>> Hello,
>>
>> I've updated patches for std::string sanitization and disa
Hi Siddhesh,
On 16/07/18 11:00, Siddhesh Poyarekar wrote:
Hi,
This is a rewrite of the tag collision avoidance patch that Kugan had
written as a machine reorg pass back in February.
The falkor hardware prefetching system uses a combination of the
source, destination and offset to decide which
On 07/16/2018 07:46 AM, Paolo Carlini wrote:
Hi,
over the last weeks, while working on various diagnostic issues, I
noticed a few defective permerror + inform pairs. Tested x86_64-linux.
ok, thanks
--
Nathan Sidwell
On 07/16/2018 07:54 AM, Tamar Christina wrote:
> The 07/13/2018 17:46, Jeff Law wrote:
>> On 07/12/2018 11:39 AM, Tamar Christina wrote:
> +
> + /* Round size to the nearest multiple of guard_size, and calculate the
> + residual as the difference between the original size and the r
Hi Sudi,
Thanks for noticing that, I have attached an improved patch file that
fixes this issue.
Below is an updated description and changelog:
This patch adds an optimisation that exploits the AArch64 BFXIL instruction
when or-ing the result of two bitwise and operations with non-overlapping
The standard doesn't specify this partial specialization (it was
required after the changes in N2637 but then should have been removed
following LWG 1262). Its presence is observable because it causes
different results when operator< has been overloaded for a shared_ptr
specialization.
PR
Committed to trunk.
commit 2a123b20c5bbb6b54d157281e2dbe546a28086f5
Author: Jonathan Wakely
Date: Mon Jul 16 18:41:31 2018 +0100
* scripts/create_testsuite_files: Fix typo in comment.
diff --git a/libstdc++-v3/scripts/create_testsuite_files
b/libstdc++-v3/scripts/create_testsui
On 07/16/2018 09:36 AM, Bernd Edlinger wrote:
Hi,
this fixes PR middle-end/86528.
Bootstrapped and reg-tested on x86_64-pc-linux-gnu.
Is it OK for trunk?
Thanks -- the string_constant change also fixes bug 86532.
There is another problem in the subsequent handling of
the CONSTRUCTOR -- it i
On July 16, 2018 5:36:22 PM GMT+02:00, Bernd Edlinger
wrote:
>Hi,
>
>this fixes PR middle-end/86528.
>
>
>Bootstrapped and reg-tested on x86_64-pc-linux-gnu.
>Is it OK for trunk?
OK.
Richard.
>
>Thanks
>Bernd.
# 147 [c=8 l=4] *movdi_internal64/1
mr 9,6 # 9[c=4 l=4] *movdi_internal64/2
extsw 3,9# 141 [c=4 l=4] extendsidi2/1
.cfi_restore 31
.cfi_restore 30
.cfi_restore 29
.cfi_restore 28
blr # 149
Hi,
I occasionally get questions about powerpc64le-linux-gnu being a primary
platform
for GCC, since the release criteria don't specifically call it out (see
https://gcc.gnu.org/gcc-8/criteria.html). Currently powerpc64-linux-gnu (for
big-endian) is listed instead, which is misleading. I wonder
On 07/16/2018 12:30 PM, Bill Schmidt wrote:
> Hi,
>
> I occasionally get questions about powerpc64le-linux-gnu being a primary
> platform
> for GCC, since the release criteria don't specifically call it out (see
> https://gcc.gnu.org/gcc-8/criteria.html). Currently powerpc64-linux-gnu (for
> big
Hi,
This patch is a small part of the work I'm doing to make function
codegen/assembly independent from one another as mentioned in:
https://gcc.gnu.org/ml/gcc/2018-07/msg00210.html. It deals with clone_fn_id_num
rather than object UIDs and I figured it's better to make my first submission
wit
Am 16.07.2018 um 10:06 schrieb Janus Weil:
However, one point: I think that the warning should be under a separate
warning, which should then be enabled by -Wextra.
-Waggressive-function-elimination, could be reused for this,
or something else
I don't actually see such a flag in the manual.
Ah
testsuite/gcc.target/powerpc/loop_align.c fails with this patch. It just needs
a simple tweak to the scan-assembler line since we're no longer generating the
",,31" portion on the .p2align.
-Pat
On Fri, Jul 13, 2018 at 04:15:26PM -0700, Carl Love wrote:
> Segher, David:
>
> I reworked the patch per the first option that David gave. The tests
> divkc3-2.c, divkc3-3.c, mulkc3-2.c and mulkc3-3.c pass on Power 9 Linux
> as they did before. The tests are unsupported on Power8 Linux as they
>
Hi!
builtin_memcpy_read_str is a function meant to be called just as a callback
and verifies that we don't cross a '\0' boundary in the string. For
inline_string_cmp, we've checked that the length returned from c_getstr
is fine, so we can cross as many embedded NULs as there are within the
TREE_S
On 07/16/2018 02:41 PM, Jakub Jelinek wrote:
> Hi!
>
> builtin_memcpy_read_str is a function meant to be called just as a callback
> and verifies that we don't cross a '\0' boundary in the string. For
> inline_string_cmp, we've checked that the length returned from c_getstr
> is fine, so we can c
On 07/04/2018 04:23 AM, marxin wrote:
> gcc/ChangeLog:
>
> 2018-07-11 Martin Liska
>
> * align.h: New file.
> * config/alpha/alpha.c (alpha_align_insns_1): Use align_functions
> directly.
> * config/i386/i386.c (ix86_avoid_jump_mispredicts): Use new return type
> align
On 07/05/2018 08:48 AM, Thomas Preudhomme wrote:
> In case of high register pressure in PIC mode, address of the stack
> protector's guard can be spilled on ARM targets as shown in PR85434,
> thus allowing an attacker to control what the canary would be compared
> against. ARM does lack stack_prote
This series adds new codegen tests for converting any of our seven
floating point modes to any of those seven. It also fixes a bunch of
bugs so that these testcases pass.
Tested on powerpc64-linux {-m32,-m64} (a power7); on powerpc64le-linux,
both on power8 and on power9; and on AIX.
Also tested
The test program for ppc_float128_hw_available would always return
false, since there is a syntax error in that test program.
2018-07-16 Segher Boessenkool
gcc/testsuite/
* lib/target-supports.exp (check_ppc_float128_hw_available): Fix
syntax error.
---
gcc/testsuite/lib/tar
The libcalls for trunc and extend of a decimal float to a binary float,
and vice versa, do not have "2" in the name, although all other such
conversions do.
2018-07-16 Segher Boessenkool
* config/rs6000/rs6000.c (init_float128_ibm): Use the correct names
for conversions betwee
The current implementation leaves an unnecessary register move. It is
easier to just expand things in the expander already. This patch does
that.
2018-07-16 Segher Boessenkool
* config/rs6000/rs6000.md (truncsf2): Expand truncates of
double-double modes to SFmode directly di
This introduces four new selectors for use with Power testcases:
longdouble64, ppc_float128, ppc_float128_insns, powerpc_vsx.
2018-07-16 Segher Boessenkool
gcc/testsuite/
* lib/target-supports.exp (check_effective_target_longdouble64,
check_effective_target_ppc_float128,
They had source and destination swapped in the name.
2018-07-16 Segher Boessenkool
* config/rs6000/rs6000.c (init_float128_ibm): Use more correct names
for the conversions between TDmode and IFmode.
(init_float128_ieee): Use more correct names for the conversions
This tests the generated code for all conversions between floating point
point types, binary and decimal.
2018-07-16 Segher Boessenkool
gcc/testsuite/
* gcc.target/powerpc/convert-fp-128.c: New testcase.
* gcc.target/powerpc/convert-fp-64.c: New testcase.
---
gcc/testsuite/g
On Mon, Jul 16, 2018 at 3:24 AM, Andreas Schwab wrote:
> * config/abi/post/riscv64-linux-gnu/baseline_symbols.txt: New file.
>
I'm not familiar with the details of these baseline symbol files.
When I try running "make new-abi-baseline" on my Fedora riscv64-linux
system using top of tree,
On 16/07/18 16:37 -0700, Jim Wilson wrote:
On Mon, Jul 16, 2018 at 3:24 AM, Andreas Schwab wrote:
* config/abi/post/riscv64-linux-gnu/baseline_symbols.txt: New file.
I'm not familiar with the details of these baseline symbol files.
When I try running "make new-abi-baseline" on my Fe
On Jul 16, 2018, Tom de Vries wrote:
> On 07/16/2018 03:34 PM, Jakub Jelinek wrote:
>> So is this essentially a workaround for GDB not supporting the statement
>> frontiers?
> AFAIU now, the concept of location views addresses this problem, so yes.
Nice! A preview for what can be obtained with
* We have been dragging these around since gcc 4.x.
* Some tweaks will likely be needed, but this gets our foot
in the door.
Authors:
Fredrik Holmqvist
Jerome Duval
Augustin Cavalier
François Revol
Simon South
Jessica Hamilton
Ithamar R. Adema
Oliver Tappe
Jonathan Schleifer
On 07/16/2018 10:10 AM, Sam Tebbs wrote:
> +++ b/gcc/config/aarch64/aarch64.c
> @@ -1439,6 +1439,14 @@ aarch64_hard_regno_caller_save_mode (unsigned regno,
> unsigned,
> return SImode;
> }
>
> +/* Implement IS_LEFT_CONSECUTIVE. Check if an integer's bits are consecutive
> + ones from th
Ping #3: https://gcc.gnu.org/ml/gcc-patches/2018-06/msg01509.html
On 07/09/2018 09:13 PM, Martin Sebor wrote:
Ping #2: https://gcc.gnu.org/ml/gcc-patches/2018-06/msg01509.html
On 07/03/2018 08:12 PM, Martin Sebor wrote:
Ping: https://gcc.gnu.org/ml/gcc-patches/2018-06/msg01509.html
On 06/24/2
On 07/16/2018 09:59 PM, Kyrill Tkachov wrote:
I think this looks ok now. You'll still need a maintainer to approve it
though.
Thank you for the review Kyrill, but also apologies for wasting your
time on it. I just found that the patch breaks a test so I'm currently
reviewing it to see what's
2018-07-16 21:50 GMT+02:00 Thomas Koenig :
> Am 16.07.2018 um 10:06 schrieb Janus Weil:
>>>
>>> However, one point: I think that the warning should be under a separate
>>> warning, which should then be enabled by -Wextra.
>>> -Waggressive-function-elimination, could be reused for this,
>>> or somet
On 16 July 2018 21:38:36 CEST, Michael Ploujnikov
wrote:
>Hi,
>
>+clone_fn_ids = hash_map::create_ggc
>(1000);
Isn't 1000 a bit excessive? What about 64 or thereabouts?
thanks,
97 matches
Mail list logo
