Hi,
[ Committed as obvious as per
https://gcc.gnu.org/legacy-ml/gcc-patches/2018-12/msg00299.html . ]
https://sourceware.org/bugzilla/show_bug.cgi?id=18632
The bundled libreadline is always built, even if the system is
./configure'd --with-system-readline and the build libreadline.a is not
used.
Hi Suwa-san,
On Thu, Oct 20, 2022 at 7:58 PM Takayuki 'January June' Suwa
wrote:
>
> This patch offers an additional allocable register by RA for the CALL0
> ABI.
>
> > Register a0 holds the return address upon entry to a function, but
> > unlike the windowed register ABI, it is not reserved for
gcc/ChangeLog:
* config/riscv/riscv.md: Add atomic type attribute.
* config/riscv/sync.md: Add atomic type for atomic instructions.
---
gcc/config/riscv/riscv.md | 2 +-
gcc/config/riscv/sync.md | 15 ++-
2 files changed, 11 insertions(+), 6 deletions(-)
diff --git
Verified, committed to trunk.
On Mon, Oct 17, 2022 at 4:37 PM wrote:
>
> From: Ju-Zhe Zhong
>
> gcc/ChangeLog:
>
> * config.gcc: Add riscv-vector-builtins-bases.o and
> riscv-vector-builtins-shapes.o
> * config/riscv/riscv-vector-builtins.cc (DEF_RVV_I_OPS): New macro.
>
Verified, committed to trunk.
On Mon, Oct 17, 2022 at 4:21 PM wrote:
>
> From: Ju-Zhe Zhong
>
> gcc/ChangeLog:
>
> * config.gcc: Add gt files since function_instance is GTY ((user)).
> * config/riscv/riscv-builtins.cc (riscv_init_builtins): Add RVV
> intrinsic framework.
>
> -Original Message-
> From: Segher Boessenkool
> Sent: Friday, October 21, 2022 2:54 AM
> To: Jiang, Haochen
> Cc: gcc-patches@gcc.gnu.org; rguent...@suse.de; Liu, Hongtao
> ; ubiz...@gmail.com; richard.earns...@arm.com;
> richard.sandif...@arm.com; marcus.shawcr...@arm.com;
> kyrylo.
Hi Honza,
Gentle ping
https://gcc.gnu.org/pipermail/gcc-patches/2022-September/601934.html
gcc/ChangeLog
* ipa-inline-analysis.cc (do_estimate_edge_time): Add function attribute
judgement for INLINE_HINT_known_hot hint.
gcc/testsuite/ChangeLog:
* gcc.dg/ipa/inlinehint-6.c: New test.
--
On Wed, Oct 19, 2022 at 9:43 AM Hongtao Liu wrote:
>
> On Tue, Oct 18, 2022 at 5:18 PM Haochen Jiang via Gcc-patches
> wrote:
> >
> > Hi all,
> >
> > We would like to add one more patch to enhance the codegen with avxvnniint8.
> > Also renamed two awkward named mode_attr to make them more aligned
On Wed, Oct 19, 2022 at 9:41 AM Hongtao Liu wrote:
>
> On Tue, Oct 18, 2022 at 5:13 PM Haochen Jiang via Gcc-patches
> wrote:
> >
> > From: Kong Lingling
> >
> > Hi all,
> >
> > This is our v2 patch on AVX-VNNI-INT8. This main change in this patch is to
> > rename the previous UNSPEC_VPMADDxxx t
On Wed, Oct 19, 2022 at 2:04 PM Hongyu Wang via Gcc-patches
wrote:
>
> Hi,
>
> Here is the update patch that align the implementation to AVX-VNNI,
> and corrects some spelling error for AVX512IFMA pattern.
>
> Bootstrapped/regtested on x86_64-pc-linux-gnu and sde. Ok for trunk?
Ok for this one.
>
> Thanks for giving me a chance to test, this seems OK on Darwin (no large-scale
> fallout, anyway) ..
>
Good to hear that.
> I tested the ise046 branch which looks like it collects several of the posted
> patch
> series, so I’ve covered those too. (not had a chance to test on AVX512 yet,
> but i
On Thu, Oct 20, 2022 at 9:22 PM Thomas Schwinge wrote:
>
> Hi!
>
> On 2022-10-20T14:23:33+0200, Aldy Hernandez wrote:
> >> I understand 'r & 3' to be logically equivalent to '(r & 2) && (r & 1)',
> >> right?
> >
> > For r == 2, r & 3 == 2, whereas (r & 2) && (r & 1) == 0, so no?
>
> Thanks, and n
With commit bf9d87193528c81b076ff463ff5591e960b6ed63 we replaced
by . It now turns out we have gathered some s, sans the space
before the slash, over the years. Convert those to plain as well.
Pushed.
---
htdocs/branch-closing.html | 4 +--
htdocs/contribute.html | 2 +-
htdocs/
Hi Jakub, Tobias!
On 2022-10-20T13:15:43+0200, I wrote:
> I'm proposing the attached "Remove support for Intel MIC offloading"
Can you please confirm:
> --- a/gcc/config/i386/i386-options.cc
> +++ b/gcc/config/i386/i386-options.cc
> @@ -307,10 +307,6 @@ ix86_omp_device_kind_arch_isa (enum
> omp
For systems with HAVE_DOS_BASED_FILE_SYSTEM set, only override the
pointer if the backslash pattern matches.
Output without this patch:
.../gcc/testsuite/gcc.dg/cpp/pr71681-2.c:5:10: fatal error: a/t2.h: No such
file or directory
With patch applied, no output and the test case succeeds.
libcpp/
Tested x86_64-pc-linux-gnu, OK for trunk?
-- >8 --
Simplify several calls to build_string_literal by not requiring redundant
strlen or IDENTIFIER_* in the caller.
I also corrected a wrong comment on IDENTIFIER_LENGTH.
gcc/ChangeLog:
* tree.h (build_string_literal): New one-argument ove
With the upcoming [[assume]] work, Andrew has pointed out that
non-irange ranges are not handled in get_range_global for
SSA_NAME_IS_DEFAULT_DEF. This patch fixes the oversight.
PR c++/106654
gcc/ChangeLog:
* value-query.cc (get_range_global): Handle non integer ranges for
In auditing the UNORDERED range-op code I noticed the UNLT_EXPR entry
was missing op1_range and op2_range operators. That is, we were
missing the ability to unwind back through an UNLT_EXPR.
gcc/ChangeLog:
* range-op-float.cc (foperator_unordered_lt::op1_range): New.
(foperator_u
Hi!
On 2022-10-20T14:23:33+0200, Aldy Hernandez wrote:
>> I understand 'r & 3' to be logically equivalent to '(r & 2) && (r & 1)',
>> right?
>
> For r == 2, r & 3 == 2, whereas (r & 2) && (r & 1) == 0, so no?
Thanks, and now please let me crawl back under my stone, embarassing...
That'd rather b
On Thu, Oct 20, 2022 at 8:59 PM Mikael Morin wrote:
>
> Le 20/10/2022 à 20:56, Mikael Morin a écrit :
> >
> > Doesn't this miss a check of flag_finite_math_only to be strictly
> > equivalent? You keep that check for the two-arguments case, so I guess
> > it's not redundant?
>
> Well, the check is
On 2022-10-20 20:19, Joseph Myers wrote:
On Wed, 19 Oct 2022, Torbjörn SVENSSON via Gcc-patches wrote:
This patch stops reporting fails for Arm targets with single
precision floating point unit for types wider than 32 bits (the width
of float on arm-none-eabi).
As reported in PR102017, fenv
On Wed, Oct 12, 2022 at 07:16:20PM +0200, Andrea Parri wrote:
> > > > +Andrea, in case he has time to look at the memory model / ABI
> > > > issues.
>
> > +Jeff, who was offering to help when the threads got crossed. I'd punted on
> > a lot of this in the hope Andrea could help out, as I'
Le 19/10/2022 à 22:49, Harald Anlauf via Fortran a écrit :
Dear Fortranners,
here's another patch that improves error receovery with references
of bad array constructors leading to an ICE after a NULL pointer
dereference.
Original patch by Steve, which I amended with a logic cleanup.
Regtested
Le 20/10/2022 à 20:56, Mikael Morin a écrit :
Doesn't this miss a check of flag_finite_math_only to be strictly
equivalent? You keep that check for the two-arguments case, so I guess
it's not redundant?
Well, the check is removed in the follow-up patch, so maybe is is after all.
Hello,
Le 20/10/2022 à 16:13, Aldy Hernandez via Gcc-patches a écrit :
The finite_operands_p function was incorrectly named, as it only
returned TRUE when !NAN. This was leftover from the initial
implementation of frange. Using the maybe_isnan() nomenclature is
more consistent and easier to un
On Thu, Oct 20, 2022 at 07:34:13AM +, Jiang, Haochen wrote:
> > > + /* Argument 3 must be either zero or one. */
> > > + if (INTVAL (op3) != 0 && INTVAL (op3) != 1)
> > > +{
> > > + warning (0, "invalid fourth argument to %<__builtin_prefetch%>;"
> > > + " using one");
> >
> > "usi
On Thu, Oct 20, 2022 at 11:12:01AM +0800, Hongtao Liu wrote:
> On Thu, Oct 20, 2022 at 9:39 AM Hongtao Liu wrote:
> > On Thu, Oct 20, 2022 at 5:08 AM Segher Boessenkool
> > > Please use a separate pattern for this, and leave prefetch to mean data
> > > prefetch, as documented! Documentation you d
On 10/20/22 13:31, Ben Boeckel wrote:
On Thu, Oct 20, 2022 at 11:39:25 -0400, Jason Merrill wrote:
Oops, I was thinking this was in gcc as well. In libcpp there's
_cpp_valid_utf8 (which calls one_utf8_to_cppchar).
This routine has a lot more logic (including UCN decoding) and the
`one_utf8_to
On Wed, 19 Oct 2022, Torbjörn SVENSSON via Gcc-patches wrote:
> This patch stops reporting fails for Arm targets with single
> precision floating point unit for types wider than 32 bits (the width
> of float on arm-none-eabi).
>
> As reported in PR102017, fenv is reported as supported in recent
>
Given that omp-oacc-kernels-decompose.cc only exists on OG12, the fix
only applies to OG12.
The fail show up since "Kernels loops annotation: C and C++." as that
adds GIMPLE_DEBUG which is not handled in omp-oacc-kernels-decompose.cc
at all. (Actually, it even fails with a sorry when compiling wi
Follow up to the mainline commit (https://gcc.gnu.org/r13-3407 + backported to
OG12):
"libgomp: Add offload_device_gcn check, add requires-4a.c test"
This xfails requires-4.c on pseudo-USM systems.
As mentioned in the email for that patch OG12's unified-share memory
implemention is for pseudo-U
On Thu, Oct 20, 2022 at 10:28 AM Segher Boessenkool
wrote:
>
> On Thu, Oct 20, 2022 at 01:44:15AM +, Jiang, Haochen wrote:
> > Maybe the testcase change cause some misunderstanding and concern.
> >
> > Actually, the patch did not disrupt the previous builtins, as the
> > builtin_prefetch
> >
The attached patch corrects a couple uninitialized variable warnings.
The variables are initialized to NULL and tested for this, calling
gcc_unreachable(). Replace other calls to abort() for with
gcc_unreachable().
Thanks to Jan-Benedict Glaw for bringing this to my attention.
** I'm receivin
On Thu, Oct 20, 2022 at 11:39:25 -0400, Jason Merrill wrote:
> Oops, I was thinking this was in gcc as well. In libcpp there's
> _cpp_valid_utf8 (which calls one_utf8_to_cppchar).
This routine has a lot more logic (including UCN decoding) and the
`one_utf8_to_cppchar` also supports out-of-bounds
On Wed, Oct 12, 2022 at 2:18 PM Jeff Law via Gcc-patches <
gcc-patches@gcc.gnu.org> wrote:
>
> On 9/25/22 09:49, linted via Gcc-patches wrote:
> > Hello,
> > I'm just checking to see if anyone has had a chance to look at this.
> >
> > Thank you
> >
> > On Wed, Sep 14, 2022 at 2:09 PM linted wrote
On Thu, Oct 20, 2022 at 01:44:15AM +, Jiang, Haochen wrote:
> Maybe the testcase change cause some misunderstanding and concern.
>
> Actually, the patch did not disrupt the previous builtins, as the
> builtin_prefetch
> uses vargs. I set the default value of the new parameter as data prefetch
commit e034c5c895722e0092d2239cd8c2991db77d6d39
Author: Jakub Jelinek
Date: Sat Dec 2 08:54:47 2017 +0100
PR target/78643
PR target/80583
* expr.c (get_inner_reference): If DECL_MODE of a non-bitfield
is BLKmode for vector field with vector raw mode, use TYPE_MOD
The attached patch corrects a couple uninitialized variable warnings.
The variables are initialized to NULL and tests for this, calling
gcc_unreachable(). Replace other calls to abort() for with
gcc_unreachable().
Thanks to Jan-Benedict Glaw for bringing this to my attention.
** I'm receiving
On Thu, Oct 20, 2022 at 04:43:06PM +, Joseph Myers wrote:
> On Thu, 20 Oct 2022, Martin Liška wrote:
>
> > > Also, but not strictly part of the release issue:
> > >
> > > (d) Builds with missing or old Sphinx should work regardless of whether
> > > such files are in the source directory - bu
The false side of UNORDERED_ means neither operand can be a NAN.
Adjust all the op[12]_range entries for the UNORDERED operators such
that a known NAN on one operands means the other operands is
undefined.
gcc/ChangeLog:
* range-op-float.cc (foperator_unordered_le::op1_range): Adjust
On Thu, 20 Oct 2022, Martin Liška wrote:
> > Also, but not strictly part of the release issue:
> >
> > (d) Builds with missing or old Sphinx should work regardless of whether
> > such files are in the source directory - but if they aren't in the source
> > directory, the effect of missing or ol
Hi,
This patch fixes the following compilation error:
../.././c++tools/server.cc: In function ‘void server(bool, int,
module_resolver*)’:
../.././c++tools/server.cc:756:69: error: ‘readers’ was not declared
in this scope; did you mean ‘read’?
756 | if (active < 0 && sock_fd >= 0 &
On 9/17/22 10:31, Patrick Palka wrote:
On Sat, 17 Sep 2022, Jason Merrill wrote:
On 9/16/22 10:59, Patrick Palka wrote:
On Fri, 16 Sep 2022, Jason Merrill wrote:
On 9/15/22 11:58, Patrick Palka wrote:
Here we're crashing during constraint matching for the instantiated
hidden friends due to
This patch adds duplicate checking for OpenMP "map" clauses, taking some
cues from the implementation for C in c-typeck.cc:c_finish_omp_clauses
(and similar for C++).
In addition to the existing use of the "mark" and "comp_mark" bitfields
in the gfc_symbol structure, the patch adds several new bit
Removed after a discussion with Jan-Benedict. He's currently working
on his testing infrastructure.
Cheers,
Martin
---
htdocs/style.mhtml | 1 -
1 file changed, 1 deletion(-)
diff --git a/htdocs/style.mhtml b/htdocs/style.mhtml
index 0790a972..08def35e 100644
--- a/htdocs/style.mhtml
+++ b/htdo
This enables us to provide symbols for placeholders and numeric limits,
and allows users to mess about with linker flags less.
libstdc++-v3/ChangeLog:
* Makefile.am [!_GLIBCXX_HOSTED]: Enable src/ subdirectory.
* Makefile.in: Regenerate.
* src/Makefile.am [!_GLIBCXX_HOSTED
On 10/20/22 17:35, Joseph Myers wrote:
> On Thu, 20 Oct 2022, Martin Liška wrote:
>
>>> Could generated man and info pages be provided as a tarball on
>>> gcc.gnu.org or ftp.gnu.org?
>>
>> Not planning doing that.
>
> Release tarballs (but not snapshots) currently include the info files and
> ma
On 10/18/22 08:18, Ben Boeckel wrote:
On Tue, Oct 11, 2022 at 07:42:43 -0400, Ben Boeckel wrote:
On Mon, Oct 10, 2022 at 17:04:09 -0400, Jason Merrill wrote:
Can we share utf8 parsing code with decode_utf8_char in pretty-print.cc?
I can look at factoring that out. I'll have to decode its logi
On Thu, 20 Oct 2022, Martin Liška wrote:
> > Could generated man and info pages be provided as a tarball on
> > gcc.gnu.org or ftp.gnu.org?
>
> Not planning doing that.
Release tarballs (but not snapshots) currently include the info files and
man pages, via gcc_release running a build with
--e
Hi Hongtao,
> On 20 Oct 2022, at 10:20, Hongtao Liu wrote:
>
> On Thu, Oct 20, 2022 at 5:17 PM Iain Sandoe wrote:
>>
>>
>>
>>> On 20 Oct 2022, at 10:09, Hongtao Liu via Gcc-patches
>>> wrote:
>>>
>>> On Thu, Oct 20, 2022 at 9:11 AM Hongtao Liu wrote:
On Wed, Oct 19, 2022 at 7:
On 20/10/2022 15:47, Kyrylo Tkachov via Gcc-patches wrote:
Hi Andrea,
-Original Message-
From: Gcc-patches On Behalf Of Andrea
Corallo via Gcc-patches
Sent: Friday, August 12, 2022 4:31 PM
To: Andrea Corallo via Gcc-patches
Cc: Richard Earnshaw ; nd
Subject: [PATCH 7/15] arm: Emit
This slightly lowers the dependency of generated code on libstdc++.so.
libstdc++-v3/ChangeLog:
* include/std/functional: Make placeholders inline, if possible.
---
libstdc++-v3/include/std/functional | 66 -
1 file changed, 37 insertions(+), 29 deletions(-)
d
> -Original Message-
> From: Andrea Corallo
> Sent: Thursday, September 29, 2022 4:46 PM
> To: Kyrylo Tkachov
> Cc: Andrea Corallo via Gcc-patches ; Richard
> Earnshaw ; nd
> Subject: [PATCH 12/15 V2] arm: implement bti injection
>
> Kyrylo Tkachov writes:
>
> > Hi Andrea,
>
> [..
(Sorry, this is a very late reply)
> -Original Message-
> From: Gcc-patches bounces+kyrylo.tkachov=arm@gcc.gnu.org> On Behalf Of Andrea
> Corallo via Gcc-patches
> Sent: Monday, August 8, 2022 10:34 AM
> To: Richard Earnshaw
> Cc: Richard Earnshaw ; nd ;
> Andrea Corallo via Gcc-patc
On 10/19/22 03:48, Jakub Jelinek wrote:
Hi!
The excess precision support broke building skia (dependency of firefox)
on ia32 (it has something like the a constexpr variable), but as the other
cases show, it is actually a preexisting problem if one uses casts from
constants with wider floating po
On 10/20/22 10:07, Patrick Palka wrote:
Here node_template_info is overlooking that CONCEPT_DECL has TEMPLATE_INFO
too, which makes get_originating_module_decl for the CONCEPT_DECL fail to
return the corresponding TEMPLATE_DECL, which leads to an ICE from
import_entity_index while pretty printing
Hi Andrea,
> -Original Message-
> From: Gcc-patches bounces+kyrylo.tkachov=arm@gcc.gnu.org> On Behalf Of Andrea
> Corallo via Gcc-patches
> Sent: Friday, August 12, 2022 4:31 PM
> To: Andrea Corallo via Gcc-patches
> Cc: Richard Earnshaw ; nd
> Subject: [PATCH 7/15] arm: Emit build
On 10/20/22 10:38, Jakub Jelinek wrote:
On Thu, Oct 20, 2022 at 10:19:59AM -0400, Jason Merrill wrote:
I think in a template we want the same early-return behavior as in the
processing_template_decl block farther down in the function: specifically,
we want to return a CONSTRUCTOR (for which COMP
On Thu, Oct 20, 2022 at 10:19:59AM -0400, Jason Merrill wrote:
> I think in a template we want the same early-return behavior as in the
> processing_template_decl block farther down in the function: specifically,
> we want to return a CONSTRUCTOR (for which COMPOUND_LITERAL_P is true), so
> it mang
Richard Sandiford writes:
> Philipp Tomsich writes:
>> This brings the extensions detected by -mcpu=native on Ampere-1 systems
>> in sync with the defaults generated for -mcpu=ampere1.
>>
>> Note that some early kernel versions on Ampere1 may misreport the
>> presence of PAUTH and PREDRES (i.e.,
libstdc++-v3/ChangeLog:
* configure.ac: Stop generating gstdint.h.
* src/c++11/compatibility-atomic-c++0x.cc: Stop using gstdint.h.
---
> > +using guintptr_t = __UINTPTR_TYPE__;
>
> I think this should be local in the only function that uses it.
Sure.
Tested on x86_64-pc-linux-g
On 10/19/22 04:00, Jakub Jelinek wrote:
Hi!
We ICE on the following testcase during mangling, finish_compound_literal
returns for void{} void_node and the mangler doesn't handle it.
Handling void_node in the mangler seems problematic to me, because
we don't know for which case it has been create
The finite_operands_p function was incorrectly named, as it only
returned TRUE when !NAN. This was leftover from the initial
implementation of frange. Using the maybe_isnan() nomenclature is
more consistent and easier to understand.
gcc/ChangeLog:
* range-op-float.cc (finite_operand_p):
Since NANs can't appear in ranges for !HONOR_NANS, there's no reason
to set them in a VARYING range.
gcc/ChangeLog:
* value-range.h (frange::set_varying): Do not set NAN flags for
!HONOR_NANS.
* value-range.cc (frange::normalize_kind): Adjust for no NAN when
!HONOR
On Sun, Oct 16, 2022 at 07:23:05PM -0600, Sandra Loosemore wrote:
> My sense is that the first approach would be more straightforward than the
> second one, and I am willing to continue to work on that. However, I think
> I need some direction to get started, as I presently know nothing about
> cg
Here node_template_info is overlooking that CONCEPT_DECL has TEMPLATE_INFO
too, which makes get_originating_module_decl for the CONCEPT_DECL fail to
return the corresponding TEMPLATE_DECL, which leads to an ICE from
import_entity_index while pretty printing the CONCEPT_DECL's module
suffix as part
> Am 20.10.2022 um 15:59 schrieb Andre Vieira (lists) via Gcc-patches
> :
>
> Hi,
>
> The 'vect_recog_bitfield_ref_pattern' was not correctly adapting the vectype
> when widening the container.
>
> I thought the original tests covered that code-path but they didn't, so I
> added a new run
Hi,
The 'vect_recog_bitfield_ref_pattern' was not correctly adapting the
vectype when widening the container.
I thought the original tests covered that code-path but they didn't, so
I added a new run-test that covers it too.
Bootstrapped and regression tested on x86_64 and aarch64.
gcc/Cha
> Am 20.10.2022 um 14:41 schrieb Jakub Jelinek via Gcc-patches
> :
>
> On Thu, Oct 20, 2022 at 12:33:28PM +, Michael Matz wrote:
>> Hey,
>>
>>> On Thu, 20 Oct 2022, Thomas Schwinge wrote:
>>>
>>> This had been done in
>>> wwwdocs commit 5c7ecfb5627e412a3d142d8dc212f4cd39b3b73f
>>> "Docu
On Thu, 20 Oct 2022 at 13:58, Arsen Arsenović via Libstdc++
wrote:
>
> libstdc++-v3/ChangeLog:
>
> * configure.ac: Stop generating gstdint.h.
> * src/c++11/compatibility-atomic-c++0x.cc: Stop using gstdint.h.
> ---
> Tested on x86_64-pc-linux-gnu.
>
> libstdc++-v3/configure.ac
> Am 20.10.2022 um 14:49 schrieb Jakub Jelinek via Gcc-patches
> :
>
> Hi!
>
> The pr54346.c testcase FAILs on i686-linux (without -msse*) for multiple
> reasons. One is the trivial missing -Wno-psabi which the following patch
> adds, but that isn't enough. The thing is that without native
libstdc++-v3/ChangeLog:
* configure.ac: Stop generating gstdint.h.
* src/c++11/compatibility-atomic-c++0x.cc: Stop using gstdint.h.
---
Tested on x86_64-pc-linux-gnu.
libstdc++-v3/configure.ac| 6 --
libstdc++-v3/src/c++11/compatibility-atomic-c++0
Hi!
The pr54346.c testcase FAILs on i686-linux (without -msse*) for multiple
reasons. One is the trivial missing -Wno-psabi which the following patch
adds, but that isn't enough. The thing is that without native vector
support, we have VEC_PERM_EXPRs in the IL and are actually considering
the ne
Hello.
I noticed the devel/modula-2 branch contains the following dead links:
- http://www.gccsummit.org/2006
- http://www.gccsummit.org/2010/speakers.php?types=LIGHTNING
- http://floppsie.comp.glam.ac.uk/Papers/paper23/gaius-mulley-gnu-m2.pdf
- http://floppsie.comp.glam.ac.uk/Papers/paper15/mull
On Thu, Oct 20, 2022 at 12:33:28PM +, Michael Matz wrote:
> Hey,
>
> On Thu, 20 Oct 2022, Thomas Schwinge wrote:
>
> > This had been done in
> > wwwdocs commit 5c7ecfb5627e412a3d142d8dc212f4cd39b3b73f
> > "Document deprecation of OpenMP MIC offloading in GCC 12".
> >
> > I'm sad about this,
Hi David.
Thanks for the patch. Please see a few comments below.
> @@ -975,6 +978,161 @@ static tree bpf_core_compute (tree, vec
> *);
> static int bpf_core_get_index (const tree);
> static bool is_attr_preserve_access (tree);
>
> +static void
> +maybe_make_core_relo (tree expr, enum btf_c
Hey,
On Thu, 20 Oct 2022, Thomas Schwinge wrote:
> This had been done in
> wwwdocs commit 5c7ecfb5627e412a3d142d8dc212f4cd39b3b73f
> "Document deprecation of OpenMP MIC offloading in GCC 12".
>
> I'm sad about this, because -- in theory -- such a plugin is very useful
> for offloading simulation
On 10/20/22 13:55, Xi Ruoyao wrote:
> On Thu, 2022-10-20 at 13:53 +0200, Martin Liška wrote:
>> On 10/20/22 13:49, Xi Ruoyao wrote:
>>> (CC our team members.)
>>>
>>> On Thu, 2022-10-20 at 13:27 +0200, Martin Liška wrote:
> Ouch. This will be very painful for Linux From Scratch. We'll need to
> I understand 'r & 3' to be logically equivalent to '(r & 2) && (r & 1)',
> right?
For r == 2, r & 3 == 2, whereas (r & 2) && (r & 1) == 0, so no?
Aldy
Hi Richard,
> Can you do the aarch64_mov_imm changes as a separate patch? It's difficult
> to review the two changes folded together like this.
Sure, I'll send a separate patch. So here is version 2 again:
[PATCH v2][AArch64] Improve immediate expansion [PR106583]
Improve immediate expansion o
Hi!
The following testcases FAIL on i686-linux due to excess diagnostics
for -Wpsabi.
Tested on x86_64-linux with
make check-gcc
RUNTESTFLAGS='--target_board=unix\{-m32/-msse2,-m32/-mno-mmx/-mno-sse,-m64\}
i386.exp=pr107271.c btf.exp=btf-function-3.c'
and committed to trunk as obvious.
2022-10
Hi!
This patch fixes a single typo in comment.
Committed as obvious to trunk.
2022-10-20 Jakub Jelinek
* passes.cc (pass_manager::register_pass): Fix a comment
typo - copmilation -> compilation.
--- gcc/passes.cc.jj2022-10-18 10:38:48.150406180 +0200
+++ gcc/passes.cc
On Mon, 17 Oct 2022 at 17:27, Patrick Palka via Libstdc++
wrote:
>
> It looks like the constexpr commit r13-3313-g378a0f1840e694
> caused some modules regressions:
>
> FAIL: g++.dg/modules/xtreme-header-4_b.C -std=c++2b (test for excess errors)
> FAIL: g++.dg/modules/xtreme-header_b.C -std=c+
On Thu, 2022-10-20 at 13:53 +0200, Martin Liška wrote:
> On 10/20/22 13:49, Xi Ruoyao wrote:
> > (CC our team members.)
> >
> > On Thu, 2022-10-20 at 13:27 +0200, Martin Liška wrote:
> > > > Ouch. This will be very painful for Linux From Scratch. We'll need to
> > > > add 23 Python modules to bu
On 10/20/22 13:34, Gerald Pfeifer wrote:
> On Mon, 17 Oct 2022, Martin Liška wrote:
>> All right, let me install my initial patch with the improved wording.
>
> The validator noticed a small issue which I addressed thusly (by
> moving up the - the beginning of implicitly closes a ).
>
> No wor
On 10/20/22 13:49, Xi Ruoyao wrote:
> (CC our team members.)
>
> On Thu, 2022-10-20 at 13:27 +0200, Martin Liška wrote:
>>> Ouch. This will be very painful for Linux From Scratch. We'll need to
>>> add 23 Python modules to build the documentation, while we only have 88
>>> packages in total curr
(CC our team members.)
On Thu, 2022-10-20 at 13:27 +0200, Martin Liška wrote:
> > Ouch. This will be very painful for Linux From Scratch. We'll need to
> > add 23 Python modules to build the documentation, while we only have 88
> > packages in total currently... And we don't want to omit GCC
>
Hi!
On 2022-10-18T07:41:29+0200, Aldy Hernandez wrote:
> On Mon, Oct 17, 2022 at 4:47 PM Thomas Schwinge
> wrote:
>> On 2022-10-17T15:58:47+0200, Aldy Hernandez wrote:
>> > On Mon, Oct 17, 2022 at 9:44 AM Thomas Schwinge
>> > wrote:
>> >> On 2022-10-11T10:31:37+0200, Aldy Hernandez via Gcc-p
On Thu, Oct 20, 2022 at 01:15:43PM +0200, Thomas Schwinge wrote:
> I'm proposing the attached "Remove support for Intel MIC offloading"
> (generated with 'git format-patch --irreversible-delete', and 'diff's for
> regenerated files manually snipped, to reduce its size).
ChangeLog missing, you'll n
On Mon, 17 Oct 2022, Martin Liška wrote:
> All right, let me install my initial patch with the improved wording.
The validator noticed a small issue which I addressed thusly (by
moving up the - the beginning of implicitly closes a ).
No worries - that's what validators are for. :-)
Gerald
co
On 10/20/22 04:26, Xi Ruoyao wrote:
> On Mon, 2022-10-17 at 15:28 +0200, Martin Liška wrote:
>> Hello.
>>
>> Based on the very positive feedback I was given at the Cauldron Sphinx
>> Documentation BoF,
>> I'm planning migrating the documentation on 9th November. There are still
>> some minor comm
On 10/19/22 18:30, Sandra Loosemore wrote:
> On 10/19/22 05:09, Martin Liška wrote:
>> On 10/18/22 00:26, Sandra Loosemore wrote:
>>> On 10/17/22 07:28, Martin Liška wrote:
Hello.
Based on the very positive feedback I was given at the Cauldron Sphinx
Documentation BoF,
I'm
Hi!
On 2021-11-12T06:41:41-0800, "H.J. Lu via Gcc-patches"
wrote:
> On Fri, Nov 12, 2021 at 6:27 AM Martin Liška wrote:
>> On 11/8/21 15:19, Jeff Law wrote:
>> > On 11/8/2021 2:59 AM, Jakub Jelinek via Gcc-patches wrote:
>> >> liboffloadmic is copied from upstream [...]
>> >> But I have no idea
On 10/19/22 18:42, Joseph Myers wrote:
> On Wed, 19 Oct 2022, Martin Liška wrote:
>
>>> Currently, there is a tarball with texinfo sources for all the manuals
>>> for each version.
>>
>> Well, then equivalent would be packaging all .rst files together with the
>> corresponding
>> conf.py, logo.*
HTML 5 now recommends against trailing slashes on void elements, so
it is instead of .
---
htdocs/index.html | 2 +-
htdocs/news/egcs-vcg.html | 2 +-
htdocs/news/gcse.html | 2 +-
htdocs/projects/gupc.html | 2 +-
htdocs/projects/tree-ssa/index
The reported regression of libgomp loop-14.C shows that there isn't
generally a good reliable place to insert the permute upfront so
the following simply restricts recurrence vectorization to the cases
where the latch value isn't defined by a PHI.
Bootstrapped and tested on x86_64-unknown-linux-gn
On Wed, Oct 12, 2022 at 04:05:32PM +0200, Tobias Burnus wrote:
> include/ChangeLog:
>
> * gomp-constants.h (GOMP_DEVICE_HSA): Comment (unused).
Comment out unused define.
or so, please.
> libgomp/ChangeLog:
>
> * testsuite/lib/libgomp.exp (check_effective_target_offload_device_gcn):
Hi!
On 2022-10-20T12:05:28+0200, I wrote:
> On 2022-10-14T13:38:55+, Julian Brown wrote:
>> The GCN backend uses a heuristic to determine whether to use FLAT or
>> GLOBAL addressing in a particular (offload) function: namely, if a
>> function takes a pointer-to-scalar parameter, it is assumed
Hi!
On 2022-10-14T13:38:55+, Julian Brown wrote:
> The GCN backend uses a heuristic to determine whether to use FLAT or
> GLOBAL addressing in a particular (offload) function: namely, if a
> function takes a pointer-to-scalar parameter, it is assumed that the
> pointer may refer to "flat scra
Hi!
Given:
On 2022-09-20T14:42:53+0100, Iain Sandoe via Gcc-patches
wrote:
> +1 from me …
> .. I have been maintaining something similar locally.
On 2022-09-20T17:23:15+0200, Martin Liška wrote:
> I do support that as well.
..., I have now pushed to master branch
commit 25861cf3a88a07c8dca3
1 - 100 of 122 matches
Mail list logo
