https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115134
Bug ID: 115134
Summary: Possible typo in _Grapheme_cluster_iterator iterator
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98881
--- Comment #5 from Pilar Latiesa ---
(In reply to Pilar Latiesa from comment #4)
> I can no longer reproduce the issue with 11.3 or 12.1
Because those were releases that didn't have checking enabled.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114134
--- Comment #5 from Pilar Latiesa ---
Another testcase:
struct TKey { int i, j, k, w; };
TKey Key(int x)
{ return {x, 0, x, 0}; }
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114134
--- Comment #3 from Pilar Latiesa ---
(In reply to Richard Biener from comment #2)
> I guess the testcase can be simplified to just show the return value
> handling issue.
I think this suffices:
struct TVec3D { double x, y, z; };
struct TKey
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114134
Bug ID: 114134
Summary: Extra mov instructions for simple function compared
with GCC13
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113376
--- Comment #3 from Pilar Latiesa ---
It seems that what is missing is a corresponding change in the macro definition
logic. It should have been changed to:
// Check the user-defined macro for warnings
#if defined(PSTL_USAGE_WARNINGS)
#
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113376
--- Comment #1 from Pilar Latiesa ---
(In reply to Pilar Latiesa from comment #0)
> I don't understand why all these functions are even instantiated as they
> appear to be related to the vectorization of other algorithms.
Pragma messages are
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113376
Bug ID: 113376
Summary: Confusing notes when using C++17 parallel algorithms
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113129
Pilar Latiesa changed:
What|Removed |Added
CC||pilarlatiesa at gmail dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110283
--- Comment #1 from Pilar Latiesa ---
Created attachment 55345
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55345=edit
preprocessed code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110283
Bug ID: 110283
Summary: Bogus Warray-bounds
Product: gcc
Version: 13.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110075
--- Comment #1 from Pilar Latiesa ---
I forgot to paste:
$ ./gcc-13/bin/g++ -v
Usando especificaciones internas.
COLLECT_GCC=./gcc-13/bin/g++
COLLECT_LTO_WRAPPER=/home/pililatiesa/gcc-13/libexec/gcc/x86_64-pc-linux-gnu/13.1.0/lto-wrapper
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110075
Bug ID: 110075
Summary: Bogus -Wdangling-reference
Product: gcc
Version: 13.1.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107591
--- Comment #19 from Pilar Latiesa ---
The testcase:
#include
struct TVec { double x, y, z; };
double dot(TVec const , TVec const )
{ return u.x * v.x + u.y * v.y + u.y * v.y + u.z * v.z; }
double mag(TVec const )
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107858
Bug ID: 107858
Summary: Variable in generic lambda incorrectly considered to
be a dependent name
Product: gcc
Version: 11.1.1
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107569
--- Comment #14 from Pilar Latiesa ---
I have tested the testcase in comment #1 with Clang, and I realized that Clang
trunk avoids the tailcall to sqrt even without any hint with
__builtin_unreachable: https://godbolt.org/z/5sb8bYcoq
Clang is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107569
Pilar Latiesa changed:
What|Removed |Added
CC||pilarlatiesa at gmail dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106910
--- Comment #12 from Pilar Latiesa ---
Wouldn't it make sense for scalar and vector versions to be affected by the
same options?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106910
--- Comment #9 from Pilar Latiesa ---
Thans so much for the fix.
I have tested last night (20220920) snapshot and I can confirm the testcase is
vectorized.
However, for the vectorization to kick in I had to use -fno-trapping-math. I
assume
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106654
Pilar Latiesa changed:
What|Removed |Added
CC||pilarlatiesa at gmail dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106910
Bug ID: 106910
Summary: roundss not vectorized
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101228
--- Comment #10 from Pilar Latiesa ---
I believe this was fixed for 11.2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98881
--- Comment #4 from Pilar Latiesa ---
I can no longer reproduce the issue with 11.3 or 12.1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105615
--- Comment #2 from Pilar Latiesa ---
(In reply to Patrick Palka from comment #1)
> Constraint subsumption is specified in terms of the normal form. When the
> concept C is made independent of the template parameter, the normal forms of
> C
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105615
Bug ID: 105615
Summary: Partial ordering of constraints with empty parameter
mapping
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102807
Pilar Latiesa changed:
What|Removed |Added
CC||pilarlatiesa at gmail dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102341
Pilar Latiesa changed:
What|Removed |Added
CC||pilarlatiesa at gmail dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102098
Pilar Latiesa changed:
What|Removed |Added
CC||pilarlatiesa at gmail dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101228
Pilar Latiesa changed:
What|Removed |Added
CC||pilarlatiesa at gmail dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100594
Pilar Latiesa changed:
What|Removed |Added
CC||pilarlatiesa at gmail dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100091
--- Comment #4 from Pilar Latiesa ---
> Of course such use of a lambda is quite pointless
Not as pointless as it might appear. This defaulted template parameter enables
a form of stateful metaprogramming:
#include
template
class T {};
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100091
Bug ID: 100091
Summary: decltype([]{}) rejected as a default template
parameter
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99522
Bug ID: 99522
Summary: Using the unseq execution policy in min_element
requires the sequence value type to be copy assignable
Product: gcc
Version: 10.2.0
Status:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99182
Bug ID: 99182
Summary: Misleading fixit hint for misspelled Greek letter
identifiers
Product: gcc
Version: 10.2.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98881
--- Comment #3 from Pilar Latiesa ---
Including vector + any header from range-v3 also triggers the ICE.
For example (https://godbolt.org/z/qnMe45):
module;
#include
#include
export module M;
void f()
{
std::vector v;
};
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98895
--- Comment #2 from Pilar Latiesa ---
(In reply to cqwrteur from comment #0)
> If those issues cannot be solved, I am sorry, I would only say C++20 modules
> failed completely.
What do you expect from being so offensive? Is this comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98885
--- Comment #8 from Pilar Latiesa ---
(In reply to Nathan Sidwell from comment #7)
That works. Thanks so much.
When there are several partitions involved it is not entirely clear to me what
declarations are first seen by the compiler compared
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98885
--- Comment #6 from Pilar Latiesa ---
(In reply to Nathan Sidwell from comment #5)
> your A-impl.cpp needs `import :B` and vice-versa
Yep. Thanks. But that's not enough for it to compile:
A-impl.cpp:7:17: error: invalid use of incomplete type
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98885
--- Comment #4 from Pilar Latiesa ---
I tried:
$ cat M.cpp
export module M;
export import :A;
export import :B;
$ cat A.cpp
export module M:A;
export class B;
export
class A
{
void
f(B const &) const;
};
$ cat B.cpp
export module
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98885
--- Comment #2 from Pilar Latiesa ---
(In reply to Nathan Sidwell from comment #1)
> This is ill-formed. an exported entity must be so-declared on its first
> declaration.
>
> A diagnostic is missing on the definition of the class.
I see.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98885
Bug ID: 98885
Summary: [modules] forward declaration of classes prevent them
from being exported at the point of actual declaration
Product: gcc
Version: 11.0
Status:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98881
Bug ID: 98881
Summary: [modules] internal compiler error: in tpl_parms_fini,
at cp/module.cc:9933
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98770
Bug ID: 98770
Summary: [modules] including certain stdlib headers in the
global module fragment of different modules causes
conflicting global module declarations
Product:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96331
Pilar Latiesa changed:
What|Removed |Added
CC||pilarlatiesa at gmail dot com
---
44 matches
Mail list logo
