On Wed, May 18, 2022 at 3:16 PM Andrew MacLeod wrote:
>
> On 5/18/22 02:41, Richard Biener wrote:
> > On Tue, May 17, 2022 at 8:41 PM Andrew MacLeod via Gcc-patches
> > wrote:
> >> This patch implements side effects of the second operand of a shift
> >> operation.
> >>
> >> given A >> B or A <<
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105652
Bug ID: 105652
Summary: ICE: in is_base_type, at dwarf2out.cc:13400
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105650
Hongtao.liu changed:
What|Removed |Added
CC||crazylht at gmail dot com
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105643
--- Comment #3 from Levy Hsu ---
I forgot to mention, that the build time also increased by 128% on the Intel
platform above, but no performance improvement was spotted.
I'll check the objdump and see what happens.
This patch to the Go frontend by Julia Lapenko traverses expressions
when exporting constants. When exporting a constant A that is
expressed through a constant B from another package, it is necessary
to traverse an expression representing the constant A to generate a
sequence of type casts from
Hello,
Should I commit to devel/omp/gcc-11 branch?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105473
--- Comment #19 from harper at msor dot vuw.ac.nz ---
Thank you. To make the outputs from my test program testdecimal.f90 easier
to compare when using different compilers, and to clarify where a reading
error happened, I have revised the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105651
Andrew Pinski changed:
What|Removed |Added
Component|c++ |tree-optimization
Known to fail|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105651
--- Comment #1 from James McKelvey ---
Created attachment 52991
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52991=edit
save-temps
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105651
Bug ID: 105651
Summary: Failure compiling constexpr/__builtin_memcpy on Cygwin
with -std=c++20
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87403
Bug 87403 depends on bug 105131, which changed state.
Bug 105131 Summary: Warning for mismatched declaration/definition with enum
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105131
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105131
Marek Polacek changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105131
--- Comment #3 from CVS Commits ---
The trunk branch has been updated by Marek Polacek :
https://gcc.gnu.org/g:7da9a089608b0ca09683332ce014fb6184842724
commit r13-627-g7da9a089608b0ca09683332ce014fb6184842724
Author: Marek Polacek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102774
Marek Polacek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102774
Barry Revzin changed:
What|Removed |Added
CC||barry.revzin at gmail dot com
---
On 5/18/22 00:26, Richard Biener wrote:
On Tue, 17 May 2022, Martin Sebor wrote:
On 5/16/22 03:16, Richard Biener wrote:
The following tries to correct get_origin_and_offset_r not handling
non-constant sizes of array elements in ARRAY_REFs and non-constant
offsets of COMPONENT_REFs. It isn't
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105650
Bug ID: 105650
Summary: [13 Regression] Possibly wrong code on fontforge
-fvect-cost-model=unlimited
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity:
Snapshot gcc-9-20220518 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/9-20220518/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 9 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105507
--- Comment #6 from Eric Botcazou ---
> So the rule of thumb is to never use -static-libgcc if you have a
> GCC-compiled DLL in the link, that's guaranteed to break otherwise.
So this could happen to the compiler if it is linked with the
On Wed, 18 May 2022, Marek Polacek via Gcc-patches wrote:
> I've extended the tests to use an enum with __attribute__ ((__packed__)) to
> test the case when the underlying type is (un)signed char. But it seems like
> we can't have underlying types wider than int. I've also included two tests
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105600
--- Comment #10 from Sam James ---
Thanks Andrew. I spent a while trying to minimise it using that but I've got a
bit stuck. I'm used to reducing normal ICEs but link-time/LTO ones seem to be
harder to me.
I was going to upload the full lot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105507
--- Comment #5 from Eric Botcazou ---
> We do have some open bugs re broken exception handling with mingw32, like
> https://github.com/msys2/MINGW-packages/issues/9289#issuecomment-945306860
>
> Sadly no one stepped up to look into that. Do
Ok.
On May 5, 2022, at 2:35 AM, Marc Poulhies via Gcc-patches
wrote:
>
> Marc Poulhiès writes:
>
>> Require effective target fpic for newly added test.
>>
>> gcc/testsuite/
>> * g++.dg/ext/visibility/visibility-local-extern1.C: Add missing
>> dg-require-effective-target fpic.
>>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105620
pc at gcc dot gnu.org changed:
What|Removed |Added
Last reconfirmed||2022-05-18
Ever confirmed|0
On Wed, May 18, 2022 at 08:58:02PM +, Joseph Myers wrote:
> On Wed, 18 May 2022, Marek Polacek via Gcc-patches wrote:
>
> > diff --git a/gcc/testsuite/gcc.dg/Wenum-int-mismatch-1.c
> > b/gcc/testsuite/gcc.dg/Wenum-int-mismatch-1.c
> > new file mode 100644
> > index 000..f71a308bc19
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105507
--- Comment #4 from Christoph Reiter ---
I see, thanks for having a look :)
We do have some open bugs re broken exception handling with mingw32, like
https://github.com/msys2/MINGW-packages/issues/9289#issuecomment-945306860
Sadly no one
On Wed, 18 May 2022, Gaius Mulley via Gcc-patches wrote:
> /* This is the contribution to the `documented_lang_options' array in
>toplev.c for gm2. */
I'm not sure what this is (an unused file?), but documented_lang_options
was removed in 2003. And in general, comments referring to .c
On Wed, 18 May 2022, Marek Polacek via Gcc-patches wrote:
> diff --git a/gcc/testsuite/gcc.dg/Wenum-int-mismatch-1.c
> b/gcc/testsuite/gcc.dg/Wenum-int-mismatch-1.c
> new file mode 100644
> index 000..f71a308bc19
> --- /dev/null
> +++ b/gcc/testsuite/gcc.dg/Wenum-int-mismatch-1.c
> @@
Commit eccbd7fcee5bbfc47731e8de83c44eee2e3dcc4b moved the subject file to
g++.target/powerpc. Unfortunately, test g++.dg/tsan/pr88018.C includes
"../pr69667.C".
Revert the move of this file.
Commit 14e678a2c4a76433fd4029568d28530c921e11ee relaxed some DejaGnu
directives in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104096
kargl at gcc dot gnu.org changed:
What|Removed |Added
CC||kargl at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105620
--- Comment #3 from CVS Commits ---
The master branch has been updated by Paul Clarke :
https://gcc.gnu.org/g:1875214cd1ca3e8bd0121f703537eb98edd84027
commit r13-626-g1875214cd1ca3e8bd0121f703537eb98edd84027
Author: Paul A. Clarke
Date:
On Wed, May 18, 2022 at 04:24:06PM -0400, Andrew MacLeod wrote:
> On 5/18/22 14:13, Segher Boessenkool wrote:
> >"Side effect" already has a meaning, very commonly used in language
> >theory, and even in the C standard itself: a function has a side effect
> >if it does something more than just
Hello,
this email contains v2:
2. the top level /gm2tools contents.
-
New file: ./ChangeLog
-
2022-05-18 Gaius Mulley
* gm2l.1: Corrected default implementation/program module
extension to .mod.
* m2color.c:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82173
--- Comment #5 from kargl at gcc dot gnu.org ---
Remove PR 82243 from "Depends On" as it isn't a PDT bug.
On 5/18/22 14:13, Segher Boessenkool wrote:
On Tue, May 17, 2022 at 02:39:11PM -0400, Andrew MacLeod via Gcc-patches wrote:
I haven't checked this patch in yet. This implements a side effect that
the divisor cannot be 0 after a divide executes. This allows us to fold
the divide away:
"Side
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105507
Eric Botcazou changed:
What|Removed |Added
Depends on||100486
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105649
Bug ID: 105649
Summary: Wrong .localentry address on powerpc64le with
-fpatchable-function-entry=1
Product: gcc
Version: 11.2.1
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105507
--- Comment #2 from Christoph Reiter ---
Stack trace (I rebuilt the host gcc 11.3.0 with debug symbols and re-ran the
failing command with "-wrapper gdb,--args"):
Thread 1 received signal SIGSEGV, Segmentation fault.
0x7563bd90 in strlen ()
On Fri, May 13, 2022 at 12:32:22PM -0500, Segher Boessenkool wrote:
> On Fri, May 13, 2022 at 11:08:48AM -0400, Michael Meissner wrote:
> > Add zero_extendditi2. Improve lxvr*x code generation.
>
>
>
> Nothing in this pass haas anything to do with the subject. Which is a
> good thing, because
On Tue, May 17, 2022 at 02:39:11PM -0400, Andrew MacLeod via Gcc-patches wrote:
> I haven't checked this patch in yet. This implements a side effect that
> the divisor cannot be 0 after a divide executes. This allows us to fold
> the divide away:
"Side effect" already has a meaning, very
The generated HTML for my GCC Newbies Guide is now at:
https://gcc-newbies-guide.readthedocs.io/en/latest/
as I seem to be unable to update the dmalcolm.fedorapeople.org
subdomain where I used to upload the HTML. Please update any links you
see to it to point to the new location.
I've also
On Tue, 2022-05-17 at 23:15 -0400, Michael Meissner wrote:
> On Fri, May 13, 2022 at 01:20:30PM -0500, will schmidt wrote:
> > On Fri, 2022-05-13 at 12:17 -0400, Michael Meissner wrote:
> > >
> > >
> > > gcc/
> > > PR target/103109
> > > * config/rs6000/rs6000.md (su_int32): New code
Hi Uros,
Very many thanks for the speedy review and approval of my ix86_rtx_costs
patch to correct the cost of multi-word multiplications. In the same
spirit, this patch tidies up a few additional nits I noticed while there:
Multi-word NOT requires two operations, but multi-word NEG requires
On Wed, May 11, 2022 at 1:52 PM H.J. Lu wrote:
>
> When -fcf-protection=branch is used, the compiler will generate jump
> tables for switch statements where the indirect jump is prefixed with
> the NOTRACK prefix, so it can jump to non-ENDBR targets. Since the
> indirect jump targets are
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41091
--- Comment #10 from Andrew Pinski ---
I really doubt there is a good solution for this because of what c++ calls
vague linkage. Clang's solution is broken too.
The patch is a revised solution for PR middle-end/98865 incorporating
the feedback/suggestions from Richard Biener's review here:
https://gcc.gnu.org/pipermail/gcc-patches/2022-May/593928.html
Most significantly, this patch now performs the transformation/optimization
during RTL expansion, where
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41091
Bobby Reynolds changed:
What|Removed |Added
CC||boreynol at microsoft dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105587
Sergei Trofimovich changed:
What|Removed |Added
CC||slyfox at gcc dot gnu.org
---
On Linux/x86_64,
eccbd7fcee5bbfc47731e8de83c44eee2e3dcc4b is the first bad commit
commit eccbd7fcee5bbfc47731e8de83c44eee2e3dcc4b
Author: Paul A. Clarke
Date: Mon Feb 21 12:14:01 2022 -0600
rs6000: Move g++.dg powerpc PR tests to g++.target
caused
FAIL: g++.dg/tsan/pr88018.C -O0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105648
Bug ID: 105648
Summary: .cfi_startproc in wrong position when
-fpatchable-function-entry= is enabled on ppc64le
Product: gcc
Version: 11.2.1
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105647
--- Comment #1 from Giuliano Belinassi ---
Confirmed.
powerpc64le-suse-linux-gcc-11 -fpatchable-function-entry=1 -O2 -c -o /tmp/a.o
pr105169_a.C
/tmp/ccjfumfv.s: Assembler messages:
/tmp/ccjfumfv.s:64: Error: .localentry expression for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98865
--- Comment #6 from CVS Commits ---
The master branch has been updated by Roger Sayle :
https://gcc.gnu.org/g:4a9be8d51182076222d707d9d68f6eda78e8ee2c
commit r13-624-g4a9be8d51182076222d707d9d68f6eda78e8ee2c
Author: Roger Sayle
Date: Wed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105627
Jakub Jelinek changed:
What|Removed |Added
Last reconfirmed||2022-05-18
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105556
Peter Bergner changed:
What|Removed |Added
Version|13.0|12.1.0
--- Comment #4 from Peter
On Wed, May 18, 2022 at 11:14:25AM +0100, Pedro Alves wrote:
> On 2022-05-18 00:56, Marek Polacek via Gcc-patches wrote:
>
> > +In C, an enumerated type is compatible with @code{char}, a signed
> > +integer type, or an unsigned integer type. However, since the choice
> > +of the underlying type
Hi Iain,
> Upstream dmd has now released v2.100.0, this patch merges in the
> latest bug fixes since the last sync-up of the release branch, as well
> as all new feature changes on development branch.
[...]
> D runtime changes:
>
> - Import druntime v2.100.0.
>
> Bootstrapped and regression
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105634
Marek Polacek changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105497
Marek Polacek changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105497
--- Comment #2 from CVS Commits ---
The trunk branch has been updated by Marek Polacek :
https://gcc.gnu.org/g:60fdce11dc9e5ddf671b07a3fc6ed70476860b22
commit r13-622-g60fdce11dc9e5ddf671b07a3fc6ed70476860b22
Author: Marek Polacek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105634
--- Comment #3 from CVS Commits ---
The trunk branch has been updated by Marek Polacek :
https://gcc.gnu.org/g:dfe38b8d5dbfe3dd5209aece4ce2f7a6b303a2f9
commit r13-621-gdfe38b8d5dbfe3dd5209aece4ce2f7a6b303a2f9
Author: Marek Polacek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105647
Bug ID: 105647
Summary: New test g++.dg/modules/pr105169 from
r13-566-g7a3f38a966a528 fails with assembler error
Product: gcc
Version: 13.0
Status: UNCONFIRMED
The problem is that subtypes are not part of the limited view of a package so
we need to use types in conjunction with limited_with clauses, which is not
always desirable since this yields less portable Ada bindings. The patch
also contains a small enhancement for complex floating-point types.
Hi all,
Tomorrow meeting will cancel since there are few new topics to discuss.
FYI,
Kito had bumped current RVV toolchain support into a rvv-next branch on
riscv-gnu-toolchain repo,
https://github.com/riscv-collab/riscv-gnu-toolchain/tree/rvv-next
Zhong Juzhe
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105645
--- Comment #1 from Andrew Pinski ---
There might be a dup of this one already.
On 5/17/22 19:57, Marek Polacek wrote:
Here we crash because we attempt to % by 0. Thus fixed.
While at it, I've moved the -Wclass-memaccess tests into warn/.
I've checked that the # of expected passes is the same before/after
the move.
Bootstrapped/regtested on x86_64-pc-linux-gnu, ok for
On 5/17/22 19:55, Marek Polacek wrote:
On Tue, May 10, 2022 at 09:54:12AM -0400, Marek Polacek wrote:
On Tue, May 10, 2022 at 08:58:46AM -0400, Jason Merrill wrote:
On 5/7/22 18:26, Marek Polacek wrote:
Corrected version that avoids an uninitialized warning:
This PR complains that we emit
On 5/17/22 12:34, Patrick Palka wrote:
On Sat, May 7, 2022 at 5:18 PM Jason Merrill wrote:
On 5/6/22 16:46, Patrick Palka wrote:
On Fri, 6 May 2022, Jason Merrill wrote:
On 5/6/22 16:10, Patrick Palka wrote:
On Fri, 6 May 2022, Patrick Palka wrote:
On Fri, 6 May 2022, Jason Merrill
Hi,
Move pr83660.C to g++.target. As comment #3 of PR83660,
renaming it to c isn't one option.
This test case isn't tested before, so this brings back
the test coverage.
Committed as r13-619-g297a69068ddfe2.
BR,
Kewen
-
gcc/testsuite/ChangeLog:
* gcc.target/powerpc/pr83660.C:
On 5/16/22 15:58, Patrick Palka wrote:
When processing a class template specialization, lookup_template_class
uses structural equality for the specialized type whenever one of its
template arguments uses structural equality. This the sensible thing to
do in a vacuum, but given that we already
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105646
--- Comment #1 from cfy1990 at gmail dot com ---
When compile without -O2, g++ will generate "'v3' may be used uninitialized"
warning.
code link: https://godbolt.org/z/r3sY4srx9
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105458
--- Comment #5 from CVS Commits ---
The releases/gcc-12 branch has been updated by Andrew Macleod
:
https://gcc.gnu.org/g:9c8125b98cdd406fbad09995529a5c6acffdd928
commit r12-8393-g9c8125b98cdd406fbad09995529a5c6acffdd928
Author: Andrew
Hi,
As PR103353 shows, we may want to continue to expand a MMA built-in
function like a normal function, even if we have already emitted
error messages about some missing required conditions. As shown in
that PR, without one explicit mov optab on OOmode provided, it would
call emit_move_insn
Hi,
As PR104482 shown, it's one regression about the handlings when
the argument number is more than the one of built-in function
prototype. The new bif support only catches the case that the
argument number is less than the one of function prototype, but
it misses the case that the argument
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105646
Bug ID: 105646
Summary: g++ does not raise xxx is used uninitialized warning
under some conditions
Product: gcc
Version: 12.1.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105645
Bug ID: 105645
Summary: Template specializations are not hidden with
fvisibility=hidden
Product: gcc
Version: 12.1.0
Status: UNCONFIRMED
Severity: normal
Richard Biener writes:
> I suggest you post merge patches where the branch touches generic code
> for review again, indicating parts that have been approved in the
> past.
Hello Richard, David and the GCC Steering Committee,
Firstly thank you for the release of gcc-12.1 and secondly thank you
Hello,
this file contains:
7. gcc/doc/gm2.texi
==
-
New file: gcc/doc/gm2.texi
-
\input texinfo
@c -*-texinfo-*-
@c Copyright (C) 2001-2022 Free Software Foundation, Inc.
@c This is part of the GM2
Hello,
this file contains:
6. gcc/m2/Make-lang.in
==
-
New file: gcc/m2/Make-lang.in
-
# Top level -*- makefile -*- fragment for GNU M2.
# Copyright (C) 2000-2022 Free Software Foundation, Inc.
Hello,
this email contains:
4. the glue code (between Modula-2 and GCC) part 3/3.
(*.def files).
New file: gcc/m2/gm2-gcc/README
This directory contains the interface code between the Modula-2 front
end and GCC. In effect this is the
hello,
this file is part-01 of the patch set for the gm2 review.
1. all GCC files which have been patched.
==
The 'Only in' diff output was:
Only in gcc-git-devel-modula2/gcc: m2
Only in gcc-git-devel-modula2/gcc/testsuite: gm2
Only in
Hello,
this email contains:
2. the top level /gm2tools contents.
---
New file: gm2tools/autogen.sh
---
#!/bin/sh
# autogen.sh regenerate the autoconf files.
# Copyright 2013-2022 Free Software Foundation, Inc.
#
# This
On 5/16/22 13:06, Marek Polacek wrote:
dynamic_cast can legally return nullptr, so I don't think it's helpful
for -Waddress to warn for
if (dynamic_cast())
// ...
More generally, it's likely not useful to warn for the artificial
POINTER_PLUS_EXPRs created by build_base_path.
Normally
On 5/18/22 02:28, Richard Biener wrote:
On Tue, May 17, 2022 at 8:40 PM Andrew MacLeod via Gcc-patches
wrote:
I haven't checked this patch in yet. This implements a side effect that
the divisor cannot be 0 after a divide executes. This allows us to fold
the divide away:
a = b / c;
if (c ==
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105644
Martin Liška changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
On 5/18/22 02:41, Richard Biener wrote:
On Tue, May 17, 2022 at 8:41 PM Andrew MacLeod via Gcc-patches
wrote:
This patch implements side effects of the second operand of a shift
operation.
given A >> B or A << B, the range of B is restricted to [0, PRECISION_A).
Fortran is currently more
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105643
Martin Liška changed:
What|Removed |Added
Last reconfirmed||2022-05-18
CC|
Hi Jakub,
Sorry for the rush of emails, I removed the Copyright part, I will use
DCO.
Note: I filled out the form.
On Wed, May 18, 2022 at 2:55 PM Mohamed Atef
wrote:
>
>
> On Wed, May 18, 2022 at 2:43 PM Jakub Jelinek wrote:
>
>> On Wed, May 18, 2022 at 02:10:29PM +0200, Mohamed Atef
On Wed, May 18, 2022 at 2:43 PM Jakub Jelinek wrote:
> On Wed, May 18, 2022 at 02:10:29PM +0200, Mohamed Atef wrote:
> > > As I said earlier, as this is just partial implementation of the
> > > OMPD, I think it would be better to commit it to a git branch but
> > > already in the upstream
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105643
Richard Biener changed:
What|Removed |Added
CC||rguenth at gcc dot gnu.org
Target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41526
Richard Biener changed:
What|Removed |Added
CC||richard at weickelt dot de
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105641
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
On Wed, May 18, 2022 at 02:10:29PM +0200, Mohamed Atef wrote:
> > As I said earlier, as this is just partial implementation of the
> > OMPD, I think it would be better to commit it to a git branch but
> > already in the upstream repository, say devel/omp/ompd branch.
> >
> > Do you have a FSF
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96710
--- Comment #2 from Jonathan Wakely ---
(In reply to Jonathan Wakely from comment #0)
> Our definitions of is_scalar depends on is_arithmetic, so
> is_scalar<__int128> is false, and therefore is_object<__int128> is false.
> This is clearly
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105639
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |12.2
Priority|P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105638
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
Hi Jakub,
This is the final patch.
I fixed things that you mentioned.
I added two more small functions at ompd-helper.c.
One more thing, the functions in ompd-helper.c are very similar. I can try
to make them generic to a single
function but, I think it's better to get the value of every ICV by
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105637
Richard Biener changed:
What|Removed |Added
Priority|P3 |P2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105635
Richard Biener changed:
What|Removed |Added
Priority|P3 |P2
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105630
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |10.4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105629
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |13.0
1 - 100 of 201 matches
Mail list logo
