> I can send the obvious patch to make it work as before and ignore the
> NULL which fixes this. I'm not sure if it should really be passing NULL
> around in the first place or not which is why I'm sharing the backtrace.
Thanks for the investigation. That's because the DECL_SOURCE_LOCATION of the
Hi!
The following patch updates from fast_float trunk. That way
it grabs two of the 4 LOCAL_PATCHES, some smaller tweaks, to_extended
cleanups and most importantly fix for the incorrect rounding case,
PR107468 aka https://github.com/fastfloat/fast_float/issues/149
Using std::fegetround showed in
Hi!
We can't handle r13-3652-ge4cba49413ca429dc82f6aa2e88129ecb3fdd943
because that commit removed whole liboffloadmic including its
ChangeLog (I'm surprised that touching ChangeLog worked out together
with removing the files), but gcc-changelog/git_update_version.py
then choked on it because it c
From: Piotr Trojanek
Attributes 'Input and 'Read are similar, but only the 'Read denotes a
subprogram with parameter of mode OUT where operand validity checks need
to be suppressed.
Cleanup related to fix for attributes 'Has_Same_Storage and
'Overlaps_Storage.
gcc/ada/
* exp_attr.adb (
From: Piotr Trojanek
Fix minor inconsistency in tags of warnings about obsolescent entities.
Part of cleaning up the warnings machinery to better handle references
to unset objects.
gcc/ada/
* sem_warn.adb (Output_Obsolescent_Entity_Warnings): Tag warnings
about obsolescent fun
From: Piotr Trojanek
Pragma Obsolescent appearing before declaration was putting the
Obsolescent flag on the Standard package, which is certainly wrong. The
problem was that we relied on the Find_Lib_Unit_Name routine without
sanitizing the pragma placement with Check_Valid_Library_Unit_Pragma.
From: Piotr Trojanek
Code cleanup; semantics is unaffected.
gcc/ada/
* sem_prag.adb (Is_In_Context_Clause): Rewrite without negations
and inequalities.
Tested on x86_64-pc-linux-gnu, committed on master.
---
gcc/ada/sem_prag.adb | 16 +---
1 file changed, 5 insert
From: Piotr Trojanek
This patch removes handling of references to unset objects that relied
on Original_Node. This handling was only needed because of rewriting
that reused operator nodes, for example, when an array inequality like:
A < B
was rewritten into:
System.Compare_Array_Unsigned_8
From: Piotr Trojanek
A recent patch removed two rewritings, where we kept the operator node
but replaced its operands. This patch removes explicit setting of the
operands; instead, the operator is already created together with its
operands, which seems a bit safer and more consistent with how we
From: Piotr Trojanek
Cleanup after replacing Unchecked_Conversion with
Ada.Unchecked_Conversion.
gcc/ada/
* libgnarl/s-interr.adb: Reorder context items and pragmas.
Tested on x86_64-pc-linux-gnu, committed on master.
---
gcc/ada/libgnarl/s-interr.adb | 17 ++---
1 file c
From: Piotr Trojanek
Whitespace cleanup only.
gcc/ada/
* libgnarl/s-interr.adb: Tune whitespace.
Tested on x86_64-pc-linux-gnu, committed on master.
---
gcc/ada/libgnarl/s-interr.adb | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/gcc/ada/libgnarl/s-in
From: Piotr Trojanek
Implement Ada 2022 4.3.4(11/5), which rejects box compound delimiter <>
in delta record aggregates, just like another rule rejects it in delta
array aggregates.
gcc/ada/
* sem_aggr.adb (Resolve_Delta_Array_Aggregate): Reject boxes in
delta array aggregates.
From: Piotr Trojanek
Code cleanup related to fixing visibility of actual parameters in
inlining-for-proof in GNATprove mode; semantics is unaffected.
gcc/ada/
* sem_ch12.adb (Check_Generic_Actuals): Remove redundant parens;
refactor an excessive if-statement; remove repeated cal
From: Steve Baird
In some cases, a Put_Image aspect specification for a scalar type was not
correctly inherited by a descendant of that type.
gcc/ada/
* exp_put_image.adb
(Image_Should_Call_Put_Image): Correctly handle the case of an
inherited Put_Image aspect specificat
From: Piotr Trojanek
Non-modified IN OUT parameters are first collected and then filtered by
examining uses of their enclosing subprograms. In this filtering we
don't need to look again at properties of the formal parameters
themselves.
Cleanup related to improved detection of references to unin
From: Steve Baird
When the binder is invoked with a "-d_c" switch, add an argument to that
switch which is the library name on the device side; so "-d_c" becomes
"-d_c=some_library_name". This does not effect the case where "-d_c" is
specified as a switch for compilation (as opposed to binding).
From: Piotr Trojanek
Move routine Enclosing_Declaration_Or_Statement from body of Sem_Res to spec
of Sem_Util, so it can be reused. In particular, GNATprove needs this
functionality to climb from an arbitrary subexpression with target_name (@)
to the enclosing assignment statement. Behaviour of t
From: Piotr Trojanek
Improve location of the comment about a special case for GNATprove mode.
gcc/ada/
* inline.adb (Establish_Actual_Mapping_For_Inlined_Call): Move
comment next to a condition that it describes.
Tested on x86_64-pc-linux-gnu, committed on master.
---
gcc/ada
From: Piotr Trojanek
Subprogram names starting with No_ seem unnecessarily confusing.
Cleanup related to improved detection of references to uninitialized
objects; semantics is unaffected.
gcc/ada/
* sem_warn.adb (Warn_On_In_Out): Remove No_ prefix; flip return
values between T
From: Piotr Trojanek
Code cleanup; issue spotted while examining routines with No_ prefix.
gcc/ada/
* mdll.ads (Build_Import_Library): Fix grammar in comment.
* mdll.adb (Build_Import_Library): Directly execute code of a
nested routine; rename No_Lib_Prefix to Strip_Lib_
From: Piotr Trojanek
When experimentally enabling frontend inlining by default, the
unnecessary call to Comes_From_Predefined_Lib_Unit in Resolve appears to
be a performance bottleneck (most likely this call is expensive because
it involves a loop over the currently inlined subprograms).
Code cl
From: Piotr Trojanek
Recently routine Safe_To_Capture_Value was adapted, so that various data
properties like validity/nullness/values are tracked also for
in-parameters. Now a similar routine Safe_To_Capture_In_Parameter_Value,
which was only used to track data nullness, is redundant, so this pa
From: Quentin Ochem
The names of imported / exported symbols were not consistent
between the device and the host when compiling for CUDA.
Remove the function Device_Ada_Final_Link_Name as it is no
longer referenced.
gcc/ada/
* bindgen.adb: fixed the way the device init and final symbol
From: Piotr Trojanek
To check if a node is located in a generic instance we can either look
at Instantiation_Location or at the Instantiation_Depth, but just
looking at the location is simpler and more efficient.
Cleanup related to improved detection of references to uninitialized
objects; seman
From: Bob Duff
Protect the building of postcondition pragmas in case the
postcondition is not present due to inlining.
gcc/ada/
* freeze.adb
(Build_Inherited_Condition_Pragmas): Do nothing if A_Post is
empty.
Tested on x86_64-pc-linux-gnu, committed on master.
---
gcc
From: Bob Duff
Print warning for a user-defined "=" that does not compose
as might be expected (i.e. is ignored for predefined "=" of
a containing record or array type). This warning is enabled by
-gnatw_q; we don't enable it by default because it generates
too many false positives. We also don't
From: Bob Duff
GNAT normally warns on "return ...;" if the "..." is known to be True or
False, but not when it is a Boolean literal True or False. This patch
also suppresses the warning when the type is derived from Boolean, and
has convention C or Fortran (and therefore True is represented as
"n
From: Bob Duff
Use named notation in calls to Expand_Composite_Equality.
gcc/ada/
* exp_ch4.adb
(Component_Equality, Expand_Array_Equality)
(Expand_Record_Equality): Use named notation.
Tested on x86_64-pc-linux-gnu, committed on master.
---
gcc/ada/exp_ch4.adb | 30 +
From: Cedric Landet
Document that gprof won't work on windows with PIE and -no-pie must be
used.
gcc/ada/
* doc/gnat_ugn/gnat_and_program_execution.rst: Mention the needed
-no-pie for windows to use gprof.
* gnat_ugn.texi: Regenerate.
Tested on x86_64-pc-linux-gnu, comm
From: Piotr Trojanek
Detection of external-vs-internal calls to protected objects relied on
the scope stack. This didn't work when the call appeared in an instance
of generic unit, because instances are analyzed in different context to
where they appear.
gcc/ada/
* exp_ch6.adb (Expand_P
From: Piotr Trojanek
Queries that ultimately examine the same field of an AST
node (e.g. Nkind) are visibly more efficient when inlined.
In particular, routines Is_Body_Or_Package_Declaration and Is_Body can
apparently be inlined into a single Nkind membership test.
This patch fixes some of the
From: Piotr Trojanek
Recently added call to In_Pragma_Expression caused a performance
regression. It might require climbing syntax trees of arbitrarily deep
expressions, while previously references within pragmas were detected in
bounded time.
This patch restores the previous efficiency. However
From: Piotr Trojanek
Tune the hash function that combines entity identifiers with source
locations of where those entities are referenced. Previously the source
location was multiplied by 2 ** 7 (i.e. shifted left by 7 bits), then
added to the entity identifier, and finally divided modulo 2 ** 16
gcc/range-op.cc:1752:16: warning: 'wi_fold' overrides a member function but is
not marked 'override' [-Winconsistent-missing-override]
gcc/range-op.cc:1757:16: warning: 'wi_op_overflows' overrides a member function
but is not marked 'override' [-Winconsistent-missing-override]
gcc/range-op.cc:175
On 11/3/22 13:32, Gerald Pfeifer wrote:
> Hi Martin,
>
> On Wed, 26 Oct 2022, Martin Liška wrote:
>> +Note the enabled sanitizer options tend to increase a false-positive rate
>> +of selected warnings, most notably @option{-Wmaybe-uninitialized}.
>> +And thus we recommend to disable @option{-Werro
Hi all,
please find attached the lastest version of this patch incorporating some
more improvents. Feel free to ignore V3.
Best Regards
Andrea
>From 869630801de2d3df03ce2f2551fd801dd59a640c Mon Sep 17 00:00:00 2001
From: Andrea Corallo
Date: Thu, 20 Jan 2022 15:36:23 +0100
Subject: [PATCH]
On Tue, 25 Oct 2022, Richard Biener wrote:
> When doing the loop unswitching re-org we promised to followup
> with improvements on the cost modeling. The following makes sure we
> try to unswitch on the most profitable condition first. As most profitable
> we pick the condition leading to the ed
The following adds a fold_builtins pass at -O0, keying off some
unwanted optimization and setting pointer alignment of the result
of __builtin_assume_alignment before removing the call. This
allows libatomic calls to be elided at -O0 on s390 for
__uint128_t foo(__uint128_t *p)
{
return __atomic
On Mon, Nov 07, 2022 at 10:02:11AM +0100, Richard Biener wrote:
> The following adds a fold_builtins pass at -O0, keying off some
> unwanted optimization and setting pointer alignment of the result
> of __builtin_assume_alignment before removing the call. This
> allows libatomic calls to be elided
On Mon, Nov 7, 2022 at 2:41 AM Haochen Jiang wrote:
>
> gcc/ChangeLog:
>
> * config/i386/i386-options.cc (m_CORE_ATOM): New.
> * config/i386/x86-tune.def
> (X86_TUNE_SCHEDULE): Initial tune for CORE_ATOM.
> (X86_TUNE_PARTIAL_REG_DEPENDENCY): Ditto.
> (X86_TU
On Sun, Nov 6, 2022 at 2:00 PM Kong, Lingling via Gcc-patches
wrote:
>
> Hi
>
> The patch is to add flag -mprefer-remote-atomic to control whether to
> generate raoint insn for atomic operations.
> Ok for trunk?
Please note TARGET_AVOID_MFENCE tuning flag, introduced a while ago
due to the fact
gcc/testsuite/ChangeLog:
* gcc.target/i386/sse-22.c: Fix typo in pragma GCC target.
Pushing as obvious.
Thanks,
Lingling
---
gcc/testsuite/gcc.target/i386/sse-22.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/testsuite/gcc.target/i386/sse-22.c
b/gcc/testsui
gcc/
* ira-color.cc (update_costs_from_allocno): Check that allocno
is in the consideration_allocno_bitmap before dereferencing
ALLOCNO_COLOR_DATA (allocno).
---
This fixes the invalid memory access, but I'm not sure if that's
sufficient and there's no remaining higher level
> index 9778e776cf2..adb1e351e15 100644
> --- a/gcc/tree-ssa-ccp.cc
> +++ b/gcc/tree-ssa-ccp.cc
> @@ -4197,6 +4197,7 @@ const pass_data pass_data_fold_builtins =
>TODO_update_ssa, /* todo_flags_finish */
> };
>
> +template
> class pass_fold_builtins : public gimple_opt_pass
> {
> public:
On Mon, 7 Nov 2022, Tamar Christina wrote:
> > -Original Message-
> > From: Richard Biener
> > Sent: Saturday, November 5, 2022 11:33 AM
> > To: Tamar Christina
> > Cc: gcc-patches@gcc.gnu.org; nd ; rguent...@suse.de
> > Subject: Re: [PATCH 1/8]middle-end: Recognize scalar reductions fro
On Mon, 7 Nov 2022, Jakub Jelinek wrote:
> On Mon, Nov 07, 2022 at 10:02:11AM +0100, Richard Biener wrote:
> > The following adds a fold_builtins pass at -O0, keying off some
> > unwanted optimization and setting pointer alignment of the result
> > of __builtin_assume_alignment before removing the
On Mon, Nov 07, 2022 at 10:31:21AM +, Richard Biener wrote:
> On Mon, 7 Nov 2022, Jakub Jelinek wrote:
>
> > On Mon, Nov 07, 2022 at 10:02:11AM +0100, Richard Biener wrote:
> > > The following adds a fold_builtins pass at -O0, keying off some
> > > unwanted optimization and setting pointer ali
> -Original Message-
> From: Richard Biener
> Sent: Monday, November 7, 2022 10:18 AM
> To: Tamar Christina
> Cc: Richard Biener ; gcc-
> patc...@gcc.gnu.org; nd
> Subject: RE: [PATCH 1/8]middle-end: Recognize scalar reductions from
> bitfields and array_refs
>
> On Mon, 7 Nov 2022, Tam
On Fri, 4 Nov 2022, Andre Vieira (lists) wrote:
> Sorry for the delay, just been reminded I still had this patch outstanding
> from last stage 1. Hopefully since it has been mostly reviewed it could go in
> for this stage 1?
>
> I addressed the comments and gave the slp-part of vectorizable_call
On Thu, 3 Nov 2022, Andre Vieira (lists) wrote:
> Hi,
>
> With Tamar's patch
> (https://gcc.gnu.org/pipermail/gcc-patches/2022-November/604880.html) enabling
> the vectorization of early-breaks, I'd like to allow bitfield lowering in such
> loops, which requires the relaxation of allowing multipl
On Mon, 7 Nov 2022, Tamar Christina wrote:
> > -Original Message-
> > From: Richard Biener
> > Sent: Monday, November 7, 2022 10:18 AM
> > To: Tamar Christina
> > Cc: Richard Biener ; gcc-
> > patc...@gcc.gnu.org; nd
> > Subject: RE: [PATCH 1/8]middle-end: Recognize scalar reductions fr
On Tue, 1 Nov 2022, Alexander Monakov wrote:
> Hi,
>
> I'm sending followup fixes for combinatorial explosion of znver scheduling
> automaton tables as described in the earlier thread:
>
> https://inbox.sourceware.org/gcc-patches/23c795d6-403c-5927-e610-f0f1215f5...@ispras.ru/T/#m36e069d43d07d
The problem here is that we are transforming a division by a power of
2 into a right shift, and using this to shift the maybe nonzero bits.
This gives the wrong result when the number being divided is negative.
In the testcase we are dividing this by 8:
[irange] int [-256, -255] NONZERO 0
> -Original Message-
> From: Richard Biener
> Sent: Monday, November 7, 2022 11:23 AM
> To: Tamar Christina
> Cc: Richard Biener ; gcc-
> patc...@gcc.gnu.org; nd
> Subject: RE: [PATCH 1/8]middle-end: Recognize scalar reductions from
> bitfields and array_refs
>
> On Mon, 7 Nov 2022, Tam
On Fri, Nov 4, 2022 at 8:53 PM Jakub Jelinek wrote:
>
> On Fri, Nov 04, 2022 at 08:14:23PM +0100, Jakub Jelinek via Gcc-patches wrote:
> > One thing that is clear is that real_isdenormal is never true for these
> > (but then a question is if flush_denormals_to_zero actually works).
>
> So, after s
On Mon, Nov 07, 2022 at 01:35:35PM +0100, Aldy Hernandez wrote:
> Let me see if I understand you correctly...
>
> real_isdenormal is always returning false for our uses in frange? So
> instead of using real_isdenormal in flush_denormals_to_zero, perhaps
> we should be using:
>
> REAL_EXP (r) < R
On Mon, Nov 7, 2022 at 1:43 PM Jakub Jelinek wrote:
>
> On Mon, Nov 07, 2022 at 01:35:35PM +0100, Aldy Hernandez wrote:
> > Let me see if I understand you correctly...
> >
> > real_isdenormal is always returning false for our uses in frange? So
> > instead of using real_isdenormal in flush_denorm
On Mon, Nov 07, 2022 at 01:48:28PM +0100, Aldy Hernandez wrote:
> On Mon, Nov 7, 2022 at 1:43 PM Jakub Jelinek wrote:
> >
> > On Mon, Nov 07, 2022 at 01:35:35PM +0100, Aldy Hernandez wrote:
> > > Let me see if I understand you correctly...
> > >
> > > real_isdenormal is always returning false for
On Fri, Oct 28, 2022 at 3:39 PM Dimitrije Milosevic
wrote:
>
> Hi Richard,
>
> > It's n_invs + 2 * n_cands?
>
> Correct, n_invs + 2 * n_cands, my apologies.
>
> > The comment says we want to prefer eliminating IVs over invariants. Your
> > patch
> > undoes that by weighting invariants the same s
On Mon, 7 Nov 2022 at 06:51, LIU Hao via Gcc wrote:
>
> 在 2022-11-07 12:37, Andrew Pinski 写道:
> >
> > The original code which used pthread was added in GCC 5 way before GCC
> > moved to being written in C++11 which was only in the last 3 years.
> > pthread_* functions were the best choice at the t
Avoid moving pure/const calls that may return twice in tree-ssa-sink:
properly redirecting the associated abnormal edge is non-trivial.
gcc/ChangeLog:
PR tree-optimization/107505
* tree-ssa-sink.cc (statement_sink_location): Additionally
reject ECF_RETURNS_TWICE calls.
gc
Hi Martin,
here is the revised patch having applied all previous recommendations:
https://gcc.gnu.org/pipermail/gcc-patches/2022-October/603436.html
Is this ok now? Thanks for the improvement suggestions (argparse
results in fewer lines of code :-)
regards,
Gaius
--8<--8<-
On Mon, 31 Oct 2022, Tamar Christina wrote:
> > > This moves the pattern detection to match.pd instead.
> >
> > where's the other copy and is it possible to remove it with this patch?
> >
>
> It looks like it's spread over various passes. Starting with forwardprop.
Can you be more specific? I
On Mon, 31 Oct 2022, Tamar Christina wrote:
> Hi All,
>
> This adds a new optab and IFNs for REDUC_PLUS_WIDEN where the resulting
> scalar reduction has twice the precision of the input elements.
>
> At some point in a later patch I will also teach the vectorizer to recognize
> this builtin once
On Mon, 31 Oct 2022, Tamar Christina wrote:
> Hi All,
>
> Here's a respin addressing review comments.
>
> Bootstrapped Regtested on aarch64-none-linux-gnu, x86_64-pc-linux-gnu
> and no issues.
>
> Ok for master?
>
> Thanks,
> Tamar
>
> gcc/ChangeLog:
>
> * match.pd: Add bitfield and sh
在 2022-11-07 20:57, Jonathan Wakely 写道:
It would be a lot nicer if playback::context met the C++ Lockable
requirements, and playback::context::compile () could just take a
scoped lock on *this:
Yeah yeah that makes a lot of sense. Would you please just commit that? I don't have write access t
On Wed, Nov 2, 2022 at 9:40 AM Dimitrije Milosevic
wrote:
>
> Hi Jeff,
>
> > This is exactly what I was trying to get to. If the addressing mode
> > isn't supported, then we shouldn't be picking it as a candidate. If it
> > is, then we've probably got a problem somewhere else in this code and
>
On Mon, 7 Nov 2022 at 08:19, Jakub Jelinek wrote:
>
> Hi!
>
> The following patch updates from fast_float trunk. That way
> it grabs two of the 4 LOCAL_PATCHES, some smaller tweaks, to_extended
> cleanups and most importantly fix for the incorrect rounding case,
> PR107468 aka https://github.com/
image.aspx
Description: Binary data
On Wed, 2 Nov 2022 at 09:26, Jakub Jelinek wrote:
>
> Hi!
>
> The following patch adds std::{to,from}_chars support for std::float128_t
> on glibc 2.26+ for {i?86,x86_64,ia64,powerpc64le}-linux.
> When long double is already IEEE quad, previous changes already handle
> it by using long double over
On 11/7/22 14:09, Gaius Mulley wrote:
>
> Hi Martin,
>
> here is the revised patch having applied all previous recommendations:
>
> https://gcc.gnu.org/pipermail/gcc-patches/2022-October/603436.html
Hi.
>
> Is this ok now? Thanks for the improvement suggestions (argparse
> results in few
> This was introduced with the fix and backports of PR103530 on
> x86_64-linux-gnux32 with older glibc versions (checked with 2.31), where
> dladdr is still in the libdl.so library, and not included in libc.so as in
> newer glibc versions.
> Linking of libgnat.so fails with
>
> [...]
> /usr/x86_64
On Mon, 7 Nov 2022 at 13:33, LIU Hao wrote:
>
> 在 2022-11-07 20:57, Jonathan Wakely 写道:
> > It would be a lot nicer if playback::context met the C++ Lockable
> > requirements, and playback::context::compile () could just take a
> > scoped lock on *this:
> >
> >
>
> Yeah yeah that makes a lot of sen
On Sat, 5 Nov 2022, Philipp Tomsich wrote:
> Alexander,
>
> I had missed your comment until now.
Please make sure to read replies from Jeff and Palmer as well (their responses
went to gcc-patches with empty Cc list):
https://inbox.sourceware.org/gcc-patches/ba895f78-7f47-0f4-5bfe-e21893c4...@
Ping.
On Fri, Oct 28, 2022 at 04:42:33PM -0400, Marek Polacek via Gcc-patches wrote:
> Two things here:
>
> 1) when we're pointing out that std::move on a constant object is
>redundant, don't say "in return statement" when we aren't in a
>return statement;
> 2) suppress the warning when t
On Thu, 27 Oct 2022, Patrick Palka wrote:
> On Thu, 27 Oct 2022, Patrick Palka wrote:
>
> > This also implements the proposed resolutions of the tentatively ready
> > LWG issues 3760 and 3761.
> >
> > I'm not sure how/if we should implement the recommended practice of:
> >
> > difference_type
On 07/11/2022 11:05, Richard Biener wrote:
On Fri, 4 Nov 2022, Andre Vieira (lists) wrote:
Sorry for the delay, just been reminded I still had this patch outstanding
from last stage 1. Hopefully since it has been mostly reviewed it could go in
for this stage 1?
I addressed the comments and g
On Wed, Nov 2, 2022 at 4:37 AM Hongyu Wang wrote:
>
> Hi, this is the updated patch of
> https://gcc.gnu.org/pipermail/gcc-patches/2022-October/604345.html,
> which uses targetm.loop_unroll_adjust as gate to enable small loop unroll.
>
> This patch does not change rs6000/s390 since I don't have ma
This allows loop unswitching to unswitch outer loops conditions are
invariant in. We restrict ourselves to unswitch conditions in innermost
loops and will only unswitch loop nests that do not contain any sibling loops.
To simplify the implementation the loop nest unswitched is the deepest all
unsw
On Mon, 7 Nov 2022, Andre Vieira (lists) wrote:
>
> On 07/11/2022 11:05, Richard Biener wrote:
> > On Fri, 4 Nov 2022, Andre Vieira (lists) wrote:
> >
> >> Sorry for the delay, just been reminded I still had this patch outstanding
> >> from last stage 1. Hopefully since it has been mostly reviewe
image.aspx
Description: Binary data
Fair enough.
How's this?
Tested on x86-64 Linux. LAPACK regression testing as well.
On Mon, Nov 7, 2022 at 1:56 PM Jakub Jelinek wrote:
>
> On Mon, Nov 07, 2022 at 01:48:28PM +0100, Aldy Hernandez wrote:
> > On Mon, Nov 7, 2022 at 1:43 PM Jakub Jelinek wrote:
> > >
> > > On Mon, Nov 07, 2022
Ping patch:
| Date: Tue, 1 Nov 2022 22:40:43 -0400
| Subject: [PATCH 1/3] Rework 128-bit complex multiply and divide, PR
target/107299
| Message-ID:
This patch is needed to build GCC on Fedora 36 where the default for long
double is now IEEE 128-bit.
--
Michael Meissner, IBM
PO Box 98, Ayer,
On Fri, Nov 4, 2022 at 8:14 PM Jakub Jelinek wrote:
>
> On Mon, Oct 17, 2022 at 08:21:01AM +0200, Aldy Hernandez wrote:
> > +// Set VALUE to its next real value, or INF if the operation overflows.
> > +
> > +inline void
> > +frange_nextafter (enum machine_mode mode,
> > + REAL_VALUE_
Ping patch:
| Date: Tue, 1 Nov 2022 22:42:30 -0400
| Subject: [PATCH 2/3] Make __float128 use the _Float128 type, PR target/107299
| Message-ID:
This patch is needed to build GCC on Fedora 36 which has switched the long
double default to be IEEE 128-bit.
--
Michael Meissner, IBM
PO Box 98, Aye
Ping patch:
| Date: Tue, 1 Nov 2022 22:44:01 -0400
| Subject: [PATCH 3/3] Update float 128-bit conversions, PR target/107299.
| Message-ID:
This patch fixes some issues with IEEE 128-bit long doubles once the previous 2
patches have been applied.
--
Michael Meissner, IBM
PO Box 98, Ayer, Massa
On Wed, 2 Nov 2022, Jakub Jelinek via Gcc-patches wrote:
> APIs. So that one can build gcc against older glibc and then compile
> user programs on newer glibc, the patch uses weak references unless
> gcc is compiled against glibc 2.26+. strfromf128 unfortunately can't
This support for older gli
On 11/7/22 01:01, Eric Botcazou via Gcc-patches wrote:
I can send the obvious patch to make it work as before and ignore the
NULL which fixes this. I'm not sure if it should really be passing NULL
around in the first place or not which is why I'm sharing the backtrace.
Thanks for the investiga
Ping x3.
On 2022/10/31 10:18 PM, Chung-Lin Tang wrote:
> Ping x2.
>
> On 2022/10/17 10:29 PM, Chung-Lin Tang wrote:
>> Ping.
>>
>> On 2022/9/21 3:45 PM, Chung-Lin Tang via Gcc-patches wrote:
>>> Hi Tom,
>>> I had a patch submitted earlier, where I reported that the current way of
>>> implementin
> Eric, can you push the approved fix for this issue (look for a message
> from Richard P day or two back, approved by Richi)? I'm dealing with a
> medical issue and heading offline again momentarily.
Sure, done.
--
Eric Botcazou
On Thu, 6 Oct 2022 at 20:03, Charles-Francois Natali via Libstdc++
wrote:
>
> `basic_filebuf::xsputn` would bypass the buffer when passed a chunk of
> size 1024 and above, seemingly as an optimisation.
>
> This can have a significant performance impact if the overhead of a
> `write` syscall is non
On Thu, 27 Oct 2022 at 19:48, Patrick Palka via Libstdc++
wrote:
>
> On Thu, 27 Oct 2022, Patrick Palka wrote:
>
> > This also implements the proposed resolutions of the tentatively ready
> > LWG issues 3760 and 3761.
> >
> > I'm not sure how/if we should implement the recommended practice of:
> >
On Mon, 7 Nov 2022 at 16:11, Joseph Myers wrote:
>
> On Wed, 2 Nov 2022, Jakub Jelinek via Gcc-patches wrote:
>
> > APIs. So that one can build gcc against older glibc and then compile
> > user programs on newer glibc, the patch uses weak references unless
> > gcc is compiled against glibc 2.26+.
On Mon, 7 Nov 2022, Jonathan Wakely wrote:
> This seems to "fix" it (not sure if it's right though):
>
> #ifndef _GLIBCXX_HAVE_FLOAT128_MATH
> extern "C" _Float128 __strtof128(const char*, char**)
> __attribute__((__weak__));
> #endif
> extern "C" _Float128 __strtof128(const char*, char**)
> __
I found some additional cases when working on the demangler. May as
well check their mangling. Since I managed to confuse myself.
nathan
--
Nathan SidwellFrom 51d567d4d15e78b42d2ca83f229c98fff2aec9fa Mon Sep 17 00:00:00 2001
From: Nathan Sidwell
Date: Mon, 7 Nov 2022 11:08:21 -0500
Subject: [
The docs say we take ISA strings, but that's never really been the case:
at a bare minimum we've required lower case strings, but there's
generally been some subtle differences as well in things like version
handling and such. We talked about removing the lower case requirement
in the last GNU too
On Thu, 03 Nov 2022 12:11:31 PDT (-0700), christoph.muell...@vrull.eu wrote:
On Wed, Nov 2, 2022 at 7:12 PM Palmer Dabbelt wrote:
On Wed, 02 Nov 2022 10:19:15 PDT (-0700), gcc-patches@gcc.gnu.org wrote:
> Could you add some test cases?
Also documentation, and ideally some sort of spec for wha
On Mon, Nov 07, 2022 at 05:48:42PM +, Jonathan Wakely wrote:
> On Mon, 7 Nov 2022 at 16:11, Joseph Myers wrote:
> >
> > On Wed, 2 Nov 2022, Jakub Jelinek via Gcc-patches wrote:
> >
> > > APIs. So that one can build gcc against older glibc and then compile
> > > user programs on newer glibc, t
For unsigned numbers, multiplication by X, where X is a power of 2 is
[0,0][X,+INF].
This patch causes a regression to g++.dg/pr71488.C where
-Wstringop-overflow gets the same IL as before, but better ranges
cause it to issue a bogus warning. I will create a PR with some
notes.
No discernible ch
On Mon, Oct 24, 2022 at 11:28 PM Richard Biener
wrote:
>
> On Mon, Oct 24, 2022 at 10:02 PM H.J. Lu wrote:
> >
> > On Mon, Oct 24, 2022 at 12:12 AM Richard Biener
> > wrote:
> > >
> > > On Fri, Oct 21, 2022 at 6:18 PM H.J. Lu wrote:
> > > >
> > > > On Fri, Oct 21, 2022 at 2:33 AM Richard Biener
1 - 100 of 141 matches
Mail list logo
