[Bug c++/109384] New: unquoted keyword 'float' in format [-Werror=format-diag]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109384 Bug ID: 109384 Summary: unquoted keyword 'float' in format [-Werror=format-diag] Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: dam...@riscv-rocks.de Target Milestone: --- Hello together, i got the following build error gcc 13 current git: /home/damian/data/gcc13built/./prev-gcc/xg++ -B/home/damian/data/gcc13built/./prev-gcc/ -B/usr/riscv64-linux-gnu/bin/ -nostdinc++ -B/home/damian/data/gcc13built/prev-riscv64-linux-gnu/libstdc++-v3/src/.libs -B/home/damian/data/gcc13built/prev-riscv64-linux-gnu/libstdc++-v3/libsupc++/.libs -I/home/damian/data/gcc13built/prev-riscv64-linux-gnu/libstdc++-v3/include/riscv64-linux-gnu -I/home/damian/data/gcc13built/prev-riscv64-linux-gnu/libstdc++-v3/include -I/home/damian/data/gcc/libstdc++-v3/libsupc++ -L/home/damian/data/gcc13built/prev-riscv64-linux-gnu/libstdc++-v3/src/.libs -L/home/damian/data/gcc13built/prev-riscv64-linux-gnu/libstdc++-v3/libsupc++/.libs -fno-PIE -c -g -O2 -fno-checking -gtoggle -DIN_GCC -fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wmissing-format-attribute -Wconditionally-supported -Woverloaded-virtual -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Werror -DHAVE_CONFIG_H -I. -I. -I../../gcc/gcc -I../../gcc/gcc/. -I../../gcc/gcc/../include -I../../gcc/gcc/../libcpp/include -I../../gcc/gcc/../libcody -I../../gcc/gcc/../libdecnumber -I../../gcc/gcc/../libdecnumber/dpd -I../libdecnumber -I../../gcc/gcc/../libbacktrace -o riscv-common.o -MT riscv-common.o -MMD -MP -MF ./.deps/riscv-common.TPo ../../gcc/gcc/common/config/riscv/riscv-common.cc ../../gcc/gcc/common/config/riscv/riscv-common.cc: In static member function 'static riscv_subset_list* riscv_subset_list::parse(const char*, location_t)': ../../gcc/gcc/common/config/riscv/riscv-common.cc:1158:48: error: unquoted keyword 'float' in format [-Werror=format-diag] 1158 | "%<-march=%s%>: z*inx is conflict with float extensions", Damian
[Bug target/102146] [11 regression] several test cases fails after r11-8940
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102146 --- Comment #22 from CVS Commits --- The master branch has been updated by HaoChen Gui : https://gcc.gnu.org/g:0580ea4b7a6dc8ee981b08f936b3ce62c6dfe200 commit r13-6981-g0580ea4b7a6dc8ee981b08f936b3ce62c6dfe200 Author: Haochen Gui Date: Fri Mar 31 12:51:32 2023 +0800 rs6000: Modify test case after mode promotion disabled gcc/testsuite/ PR target/102146 * gcc.target/powerpc/pr56605.c: Modify the match pattern for dump scan.
[Bug libstdc++/109383] New: [QoI] std::type_index::operator<=> should not call __builtin_strcmp twice
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109383
Bug ID: 109383
Summary: [QoI] std::type_index::operator<=> should not call
__builtin_strcmp twice
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: de34 at live dot cn
Target Milestone: ---
The current the current implementation of type_index::operator<=> in libstdc++
is the following:
```
strong_ordering
operator<=>(const type_index& __rhs) const noexcept
{
if (*_M_target == *__rhs._M_target)
return strong_ordering::equal;
if (_M_target->before(*__rhs._M_target))
return strong_ordering::less;
return strong_ordering::greater;
}
```
When the two referenced type_info are not equal, the current implementation may
needed to call __builtin_strcmp twice (each in type_info::operator== and
type_info::before).
IIUC whenever it's necessary to call __builtin_strcmp from operator<=>, we
should just call it once and return __builtin_strcmp(...) <=> 0. Perhaps it
would be better to add a member function to type_info for convenience.
It's a bit strange to me that while all implementations I investigated (libc++,
libstdc++, and msvc stl) need to use strcmp/__builtin_strcmp for type_info
comparison in some cases, currently none of them avoids calling it twice from
type_index::operator<=>, although strcmp/__builtin_strcmp is already performing
three-way comparison.
[Bug c++/103663] Diagnostic is missing multiple instantiation frames to help point to where the problem happens
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103663 Andrew Pinski changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill ||a/show_bug.cgi?id=90508 --- Comment #1 from Andrew Pinski --- Maybe similar to PR 90508.
[Bug c++/90508] GCC does not produce full template backtraces when instantiating but not calling virtual functions
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90508
--- Comment #3 from Andrew Pinski ---
Note the older gccs even get the line even more wrong, take:
```
template struct a {
int t;
virtual b g() { return 0; }
};
a t;
int tt;
a t1;
int tt1;
```
The error points to the line containing a which has no relationship to
a even.
[Bug c++/109382] Error inside virtual function of class template does not show point of instantiation/use, only shows where the function is defined.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109382 Andrew Pinski changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Andrew Pinski --- Dup of bug 90508 in the end. *** This bug has been marked as a duplicate of bug 90508 ***
[Bug c++/90508] GCC does not produce full template backtraces when instantiating but not calling virtual functions
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90508 Andrew Pinski changed: What|Removed |Added CC||zeratul976 at hotmail dot com --- Comment #2 from Andrew Pinski --- *** Bug 109382 has been marked as a duplicate of this bug. ***
[Bug c++/90508] GCC does not produce full template backtraces when instantiating but not calling virtual functions
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90508
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
Last reconfirmed||2023-04-03
--- Comment #1 from Andrew Pinski ---
Confirmed.
Reduced testcase:
```
template struct a {
virtual b g() { return 0; }
};
a t;
```
Note at first this seemed like a regression but in GCC 7 and before, the line
for the first required at was pointing to the last line of the file, now it
points to the first virtual function in the class.
[Bug c++/109382] Error inside virtual function of class template does not show point of instantiation
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109382
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
Last reconfirmed||2023-04-03
--- Comment #2 from Andrew Pinski ---
Reduced slightly more:
```
template
struct C {
virtual void f() {
T().waldo();
}
};
int main() {
C obj;
}
```
[Bug c++/109382] Error inside virtual function of class template does not show point of instantiation
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109382 --- Comment #1 from Andrew Pinski --- clang gives: :7:8: error: member reference base type 'int' is not a structure or union T().waldo(); ~~~^~ :11:10: note: in instantiation of member function 'C::f' requested here C obj; ^ Which is definitely better.
[Bug c++/109382] New: Error inside virtual function of class template does not show point of instantiation
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109382
Bug ID: 109382
Summary: Error inside virtual function of class template does
not show point of instantiation
Product: gcc
Version: 12.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: zeratul976 at hotmail dot com
Target Milestone: ---
Given the following invalid code:
struct Base {
virtual void f() = 0;
};
template
struct C : Base {
void f() override {
T().waldo();
}
};
int main() {
C obj;
}
The error is printed as follows:
$ g++-12 -c test.cpp
test.cpp: In instantiation of ‘void C::f() [with T = int]’:
test.cpp:6:8: required from here
test.cpp:7:9: error: request for member ‘waldo’ in ‘0’, which is of non-class
type ‘int’
7 | T().waldo();
| ^
The error is missing a "required from here" line pointing to `C obj;`.
If you imagine everything above main() being library code, it can be hard for a
user to tell which line of the user's code is triggering the error in the
library.
[Bug debug/44126] wrong location description for DW_AT_vtable_elem_location
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44126 --- Comment #7 from Tom Tromey --- I happened to be looking in this area and I see that gcc still generates the old, incorrect form.
[Bug c++/109381] [10/11/12/13 Regression] Ambiguous member lookup with this-> accepted when it should be rejected
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109381 Andrew Pinski changed: What|Removed |Added Status|UNCONFIRMED |NEW Keywords||needs-bisection Last reconfirmed||2023-04-03 Ever confirmed|0 |1 --- Comment #1 from Andrew Pinski --- Confirmed. most likely caused by the way which got it right without this->
[Bug c++/109381] [10/11/12/13 Regression] Ambiguous member lookup with this-> accepted when it should be rejected
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109381 Andrew Pinski changed: What|Removed |Added Known to work||7.5.0 Summary|Ambiguous member lookup |[10/11/12/13 Regression] |with this-> accepted when |Ambiguous member lookup |it should be rejected |with this-> accepted when ||it should be rejected Known to fail||13.0, 8.1.0 Target Milestone|--- |10.5
[Bug c++/109381] New: Ambiguous member lookup with this-> accepted when it should be rejected
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109381
Bug ID: 109381
Summary: Ambiguous member lookup with this-> accepted when it
should be rejected
Product: gcc
Version: unknown
Status: UNCONFIRMED
Keywords: accepts-invalid
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: arthur.j.odwyer at gmail dot com
Target Milestone: ---
// https://godbolt.org/z/ex97db8cT
template
struct B {
int f() { return 1; }
};
struct C {
int f() { return 2; }
};
template
struct D : B, C {
int test() {
return this->f(); // GCC calls C::f; Clang and MSVC reject
}
};
int main() {
D d;
return d.test();
}
This can't possibly be unreported yet, but a quick search failed to find any
bug filed on the subject. Sorry if this is a duplicate.
GCC correctly thinks that `return f();` should call `C::f` because `B::f` is
not considered because `B` is a dependent base class and we didn't say
`this->`.
But, GCC wrongly thinks that `return this->f();` should ALSO call `C::f`. Clang
and MSVC agree that it should be ambiguous, because now it IS looked up in both
phase 1 and phase 2, and an `f` is found in both base classes, so the lookup
should be considered ambiguous.
According to Godbolt, the issue was introduced somewhere between GCC 7.5 (OK)
and GCC 8.1 (buggy).
[Bug fortran/100607] ICE with SELECT RANK
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100607
kargl at gcc dot gnu.org changed:
What|Removed |Added
Keywords|ice-on-invalid-code |
Priority|P3 |P4
--- Comment #2 from kargl at gcc dot gnu.org ---
Remove ice-on-invalid-code as I don't get an ICE.
The following patch suppresses the error message with the temporary variable
and removes duplicated code. Please commit.
diff --git a/gcc/fortran/resolve.cc b/gcc/fortran/resolve.cc
index 46585879ddc..3462d43f346 100644
--- a/gcc/fortran/resolve.cc
+++ b/gcc/fortran/resolve.cc
@@ -9909,11 +9909,6 @@ resolve_select_rank (gfc_code *code, gfc_namespace
*old_ns)
|| gfc_expr_attr (code->expr1).pointer))
gfc_error ("RANK (*) at %L cannot be used with the pointer or "
"allocatable selector at %L", >where,
>expr1->where);
-
- if (case_value == -1 && (gfc_expr_attr (code->expr1).allocatable
- || gfc_expr_attr (code->expr1).pointer))
- gfc_error ("RANK (*) at %L cannot be used with the pointer or "
- "allocatable selector at %L", >where,
>expr1->where);
}
/* Add EXEC_SELECT to switch on rank. */
@@ -12948,7 +12943,9 @@ resolve_fl_var_and_proc (gfc_symbol *sym, int mp_flag)
if (allocatable)
{
- if (dimension && as->type != AS_ASSUMED_RANK)
+ if (dimension
+ && as->type != AS_ASSUMED_RANK
+ && !sym->attr.select_rank_temporary)
{
gfc_error ("Allocatable array %qs at %L must have a deferred "
"shape or assumed rank", sym->name,
>declared_at);
[Bug c++/109378] new builtin like __builtin_sqrt but does not set errno
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109378 Andrew Pinski changed: What|Removed |Added Resolution|FIXED |INVALID --- Comment #12 from Andrew Pinski --- (In reply to g.peterhoff from comment #11) > Ok, in detail: > std::sqrt/__builtin_sqrt performs the check for nan in the calling context. > This causes the following problems: It is a check for less than 0; not NAN. > * the calling context contains error handling/conditional jumps, which have > nothing to do there but have to be handled in the error handling of std::sqrt > * Because this does NOT happen in your implementation of std::sqrt, the code > gets bloated, at the latest when a function contains more than one std::sqrt. There could be a check on errno later on even ... There is no way for GCC to know that. > > Therefore > * do complete error handling in std::sqrt/__builtin_sqrt > * so there is only one exact call for std::sqrt, which can/must be > vectorized. Again it still cannot be vectorized because it needs to be exact. It is also hard to detect if errno is not being used too.
[Bug c++/109378] new builtin like __builtin_sqrt but does not set errno
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109378 g.peterh...@t-online.de changed: What|Removed |Added Resolution|INVALID |FIXED --- Comment #11 from g.peterh...@t-online.de --- Ok, in detail: std::sqrt/__builtin_sqrt performs the check for nan in the calling context. This causes the following problems: * the calling context contains error handling/conditional jumps, which have nothing to do there but have to be handled in the error handling of std::sqrt * Because this does NOT happen in your implementation of std::sqrt, the code gets bloated, at the latest when a function contains more than one std::sqrt. Therefore * do complete error handling in std::sqrt/__builtin_sqrt * so there is only one exact call for std::sqrt, which can/must be vectorized.
[Bug target/109380] inline member function symbol not exported with explicit template instantiation declaration on MinGW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109380 --- Comment #3 from Andrew Pinski --- Note there are not many folks working on mingw support for GCC these days. Also I don't work on that port, I work on other ports and try to triage bug reports which is why I commented here.
[Bug target/109380] inline member function symbol not exported with explicit template instantiation declaration on MinGW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109380 --- Comment #2 from Vittorio Romeo --- Hmm, you might be correct. Seeing that the issue has not been looked at since 2017, are you aware of any workaround besides `-Wl,--export-all-symbols`? The issue is preventing me from applying explicit template instantiations in the SFML codebase for commonly used template types.
[Bug target/109380] inline member function symbol not exported with explicit template instantiation declaration on MinGW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109380 Andrew Pinski changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill ||a/show_bug.cgi?id=81855 --- Comment #1 from Andrew Pinski --- Actually I think this is a dup of bug 81855.
[Bug c++/109378] new builtin like __builtin_sqrt but does not set errno
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109378 --- Comment #10 from Andrew Pinski --- >This would have the advantage that std::sqrt would not "contaminate" the >calling function with conditional jumps and thus inflate it. Also what do you mean by inflate it? do you mean code size? Or do you think partial inlining the error part is causing branch misses?
[Bug c++/109378] new builtin like __builtin_sqrt but does not set errno
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109378 Andrew Pinski changed: What|Removed |Added Resolution|--- |INVALID Summary|improve __builtin_sqrt |new builtin like ||__builtin_sqrt but does not ||set errno Status|UNCONFIRMED |RESOLVED --- Comment #9 from Andrew Pinski --- Then there is nothing to be done here. GCC is doing the correct thing. It is inlining the error path for better optimizations. Since you don't want to use another flag or another option, or even another builtin, there is nothing to be done here. It just sounds like you don't want to program in C/C++ because of these constraints.
[Bug c++/109380] New: inline member function symbol not exported with explicit template instantiation declaration on MinGW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109380
Bug ID: 109380
Summary: inline member function symbol not exported with
explicit template instantiation declaration on MinGW
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: vittorio.romeo at outlook dot com
Target Milestone: ---
Created attachment 54801
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54801=edit
Full example (lib.h, lib.cpp, main.cpp, build.sh)
Given the following code:
//
// lib.h
template
struct S
{
void f();
void g() { }
};
template void S::f() { }
extern template struct __declspec(dllexport) S;
//
// lib.cpp
#include "lib.h"
template struct S;
//
// main.cpp
#include "lib.h"
int main() { S{}.g(); }
When building with:
g++ -c -o main.o main.cpp && \
g++ -c -o lib.o lib.cpp && \
g++ -shared -o lib.dll lib.o -Wl,--out-implib,liblib.dll.a && \
g++ -o main.exe main.o -L. -llib
This linker error is erroneously produced:
C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/12.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe:
main.o:main.cpp:(.text+0x15): undefined reference to `S::g()'
collect2.exe: error: ld returned 1 exit status
This is likely the same as bug #89088:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89088
And probably related to this Clang PR and review:
https://reviews.llvm.org/D61118
I bumped into this issue today, using GCC version 12.2.0, on MinGW/MSYS2.
The last bug report is UNCONFIRMED since 2019.
[Bug c++/109378] new builtin like __builtin_sqrt but does not set errno
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109378 --- Comment #8 from g.peterh...@t-online.de --- But I don't want and can't use a version of std::sqrt that requires compiler specific flags/options/__builtins and injects internals of std::sqrt/__builtin_sqrt into the calling context/function. I just want to have a very dumb std::sqrt that does its error handling internally. Sorry, but is that too much to ask?
[Bug c++/89088] Dllexport for explicit template instantiation missing inline methods
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89088 Vittorio Romeo changed: What|Removed |Added CC||vittorio.romeo at outlook dot com --- Comment #2 from Vittorio Romeo --- Bumped into this issue today. I confirm that it is still present on gcc version 12.2.0, on MSYS2. Any workaround that does not require exporting all symbols via '-Wl,--export-all-symbols'?
[Bug c++/109378] new builtin like __builtin_sqrt but does not set errno
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109378
--- Comment #7 from Andrew Pinski ---
Also you could do:
template
inline constexpr Type my_sqrt(const Type x) noexcept
{
if (std::isless(x, 0.0)) __builtin_unreachable();
return std::sqrt(x);
}
And GCC will optimize away the check for negative and NAN correctly on the
trunk.
[Bug c++/109378] new builtin like __builtin_sqrt but does not set errno
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109378 --- Comment #6 from Andrew Pinski --- >Wouldn't it be better to rewrite __builtin_sqrt so that these tests are done >inside __builtin_sqrt and not already in the calling context? NO, in fact it is designed this way to better optimize sqrt in the normal case.
[Bug c++/109378] new builtin like __builtin_sqrt but does not set errno
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109378 Andrew Pinski changed: What|Removed |Added Severity|normal |enhancement
[Bug c++/109378] improve __builtin_sqrt
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109378 --- Comment #5 from Andrew Pinski --- (In reply to g.peterhoff from comment #4) > Hm. Maybe we misunderstood each other or I don't understand. I don't want to > set -fno-math-errno or any other compiler-specific flag. My intention is > that __builtin_sqrt doesn't "contaminate" the calling context with internals > of __builtin_sqrt, but simply returns the result. That is not how the builtins work ...
[Bug c++/109378] improve __builtin_sqrt
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109378 --- Comment #4 from g.peterh...@t-online.de --- Hm. Maybe we misunderstood each other or I don't understand. I don't want to set -fno-math-errno or any other compiler-specific flag. My intention is that __builtin_sqrt doesn't "contaminate" the calling context with internals of __builtin_sqrt, but simply returns the result.
[Bug target/109375] FAIL: gnat.dg/opt39.adb scan-tree-dump-not optimized "tmp"
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109375 John David Anglin changed: What|Removed |Added Resolution|--- |FIXED Status|WAITING |RESOLVED --- Comment #3 from John David Anglin --- Fixed.
[Bug target/109375] FAIL: gnat.dg/opt39.adb scan-tree-dump-not optimized "tmp"
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109375 --- Comment #2 from CVS Commits --- The master branch has been updated by John David Anglin : https://gcc.gnu.org/g:8f989fe879ddc2753ac9fa580b2b0a1024c98f0f commit r13-6978-g8f989fe879ddc2753ac9fa580b2b0a1024c98f0f Author: John David Anglin Date: Sun Apr 2 21:27:46 2023 + Fix gnat.dg/opt39.adb on hppa. Add hppa*-*-* to dg-additional-options list. 2023-04-02 John David Anglin gcc/testsuite/ChangeLog: PR target/109375 * gnat.dg/opt39.adb: Add hppa*-*-* to dg-additional-options list.
[Bug c++/109378] improve __builtin_sqrt
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109378 Andrew Pinski changed: What|Removed |Added Target||*-linux-gnu --- Comment #3 from Andrew Pinski --- (In reply to g.peterhoff from comment #2) > But this is of no use if I want to compile something "normally" without > compiler specific options. Note some libc implementations don't implement setting errno on math functions (e.g. Darwin) and for those targets, -fno-math-errno is already the default. So if you don't need to check errno, then you can use -fno-math-errno. C/C++ allows for an implementation to set errno on an error for math functions even. So this is more about you wanting something different from what the implementation does ...
[Bug c++/109378] improve __builtin_sqrt
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109378 --- Comment #2 from g.peterh...@t-online.de --- But this is of no use if I want to compile something "normally" without compiler specific options.
[Bug target/109379] improve __builtin_fmal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109379 --- Comment #2 from Andrew Pinski --- and doing it inline is not going to help that much as the overhead is not due to not being inlined; it is just an expensive operation as it has to be done using soft-float.
[Bug target/109379] improve __builtin_fmal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109379 Andrew Pinski changed: What|Removed |Added Resolution|WONTFIX |INVALID
[Bug target/109379] improve __builtin_fmal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109379 Andrew Pinski changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #1 from Andrew Pinski --- There is no way to improve fmal really. Because it requires to do the multiple and add in infinite precision and only doing the rounding afterwards.
[Bug c++/109379] New: improve __builtin_fmal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109379 Bug ID: 109379 Summary: improve __builtin_fmal Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: g.peterh...@t-online.de Target Milestone: --- Hello gcc team, __builtin_fmal generates quite a lot of overhead. Can you please optimize this or make it an inline function? thx Gero
[Bug c++/109378] improve __builtin_sqrt
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109378 --- Comment #1 from Andrew Pinski --- -fno-math-errno
[Bug c++/109378] New: improve __builtin_sqrt
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109378 Bug ID: 109378 Summary: improve __builtin_sqrt Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: g.peterh...@t-online.de Target Milestone: --- Hello gcc team, https://godbolt.org/z/Wa1rfxrPo when I write a function that contains std::sqrt, it always contains the nan(?) tests for the argument. E.g. sqrtf64. If I use my_sqrt the tests are done inside sqrt and not in the calling function - clear (because noinline). Wouldn't it be better to rewrite __builtin_sqrt so that these tests are done inside __builtin_sqrt and not already in the calling context? This would have the advantage that std::sqrt would not "contaminate" the calling function with conditional jumps and thus inflate it. I can make this clear with foo vs. bar. And of course __builtin_sqrt must be able to be vectorized automatically and must be inline for certain contexts (e.g. __FAST_MATH__). regards Gero
[Bug fortran/104272] finalizer gets called during allocate
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104272 anlauf at gcc dot gnu.org changed: What|Removed |Added CC||anlauf at gcc dot gnu.org, ||pault at gcc dot gnu.org --- Comment #1 from anlauf at gcc dot gnu.org --- This is still the case after Paul's big finalization update. Adding him in CC. @Paul: can you comment?
[Bug target/109376] FAIL: gnat.dg/prot7.adb (test for excess errors)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109376 John David Anglin changed: What|Removed |Added Status|WAITING |RESOLVED Resolution|--- |FIXED --- Comment #4 from John David Anglin --- Fixed.
[Bug target/109376] FAIL: gnat.dg/prot7.adb (test for excess errors)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109376 --- Comment #3 from CVS Commits --- The master branch has been updated by John David Anglin : https://gcc.gnu.org/g:e35503833c0418fb6a0475f6e927cbcf64814c1e commit r13-6977-ge35503833c0418fb6a0475f6e927cbcf64814c1e Author: John David Anglin Date: Sun Apr 2 20:03:48 2023 + Skip gnat.dg/prot7.adb on hppa. Test needs to be skipped if the target does not support atomic primitives. 2023-04-02 John David Anglin gcc/testsuite/ChangeLog: PR target/109376 * gnat.dg/prot7.adb: Skip on hppa.
[Bug fortran/64654] problem of handling character arguments in parent of an 'entry' with fewer arguments at -O0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64654
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Last reconfirmed|2021-12-17 00:00:00 |2023-4-2
--- Comment #3 from anlauf at gcc dot gnu.org ---
(In reply to kargl from comment #1)
> Reduced testcase.
[...]
> Workaround. Don't compile with -O0. All other optimiziation
> levels -O1, -O2, and -O3 with and without -fcheck=all compile
> and run for gfortran 5.0.
This is no longer true for 13-mainline.
Using -O1 along with -fcheck=bounds leads to a crash on x86_64-pc-linux-gnu,
and -fsanitize=undefined gives at runtime:
pr64654.f90:1:16: runtime error: load of null pointer of type 'integer(kind=4)'
The dump-tree of the subroutine shows why:
void s0 ()
{
master.0.s (1, 0B, 0B, 0);
}
void master.0.s (integer(kind=8) __entry, character(kind=1)[1:.a] * a,
integer(kind=4) * n, integer(kind=8) _a)
{
integer(kind=8) .a;
bitsizetype D.4282;
sizetype D.4283;
.a = MAX_EXPR <(integer(kind=8)) *n, 0>;
D.4282 = (bitsizetype) (sizetype) NON_LVALUE_EXPR <.a> * 8;
D.4283 = (sizetype) NON_LVALUE_EXPR <.a>;
switch (__entry)
{
case 0:;
goto L.2;
case 1:;
goto L.4;
}
I think we need to either check the presence of arguments or move the
pointer dereferences.
[Bug modula2/109336] The -fmod= and -fdef= options do not work.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109336 --- Comment #3 from CVS Commits --- The master branch has been updated by Gaius Mulley : https://gcc.gnu.org/g:5bb27a1bb2f1c0533e1dda6c4a326e50756830f1 commit r13-6976-g5bb27a1bb2f1c0533e1dda6c4a326e50756830f1 Author: Gaius Mulley Date: Sun Apr 2 20:30:43 2023 +0100 PR modula2/109336 pass -fmod= though and build m2/stage2/cc1gm2 libs This patch enables gm2 to pass -fmod= though to cc1gm2. It also builds the libraries for m2/stage2/cc1gm2 with no named path and full debugging. gcc/m2/ChangeLog: PR modula2/109336 * Make-lang.in (GM2_O): Set to -O0. (GM2_LIBS): Remove target libraries and replace with build libs. (BUILD-LIBS): New declaration. (m2/gm2-libs/libgm2.a): New rule. (m2/gm2-libs/%.o): New rule. (m2/gm2-libs/choosetemp.o): New rule. * gm2-compiler/M2ColorString.mod (append): Use ADR rather than implicit conversion. * gm2-compiler/M2Comp.mod (Compile): Add qprintf messages for when a source file is not found. Improve comments and formatting. * gm2-libs-ch/cgetopt.c (cgetopt_cgetopt_long): Remove ansi-decl.h. Add getopt.h. (cgetopt_cgetopt_long_only): Change cgetopt_ to getopt_. * gm2spec.cc (lang_specific_driver): Do not skip -fmod=. Remove comment. Signed-off-by: Gaius Mulley
[Bug fortran/103931] Type name "c_ptr" is ambiguous when iso_c_binding is imported both directly and indirectly
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103931 --- Comment #12 from anlauf at gcc dot gnu.org --- (In reply to Bernhard Reutner-Fischer from comment #11) > Both the original testcase as well as the reduced testcase from comment #2 > compile fine for me with trunk from earlier today at r13-6974-g802ab7d0db5b5a The behavior of gfortran is very fragile. Consider the original testcase. Module CModule has no public symbols. Technically, the "use CModule" in module DModule should not have any effect. (Confirmed by other brands). However, commenting the "use CModule" reproduces the original error message. This PR may be a duplicate of others that describe gfortran's confusion when using (intrinsic) modules along a module chain like here. Just try running gfortran under valgrind.
[Bug other/109306] The strstr implementation in libiberty might have undefined behavior (out of bounds mem access)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109306 Jakub Jelinek changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #8 from Jakub Jelinek --- Should be fixed now.
[Bug other/109306] The strstr implementation in libiberty might have undefined behavior (out of bounds mem access)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109306
--- Comment #7 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:1719fa40c4ee4def60a2ce2f27e17f8168cf28ba
commit r13-6975-g1719fa40c4ee4def60a2ce2f27e17f8168cf28ba
Author: Jakub Jelinek
Date: Sun Apr 2 20:05:31 2023 +0200
libiberty: Make strstr.c in libiberty ANSI compliant
On Fri, Nov 13, 2020 at 11:53:43AM -0700, Jeff Law via Gcc-patches wrote:
>
> On 5/1/20 6:06 PM, Seija Kijin via Gcc-patches wrote:
> > The original code in libiberty says "FIXME" and then says it has not
been
> > validated to be ANSI compliant. However, this patch changes the
function to
> > match implementations that ARE compliant, and such code is in the
public
> > domain.
> >
> > I ran the test results, and there are no test failures.
>
> Thanks. This seems to be the standard "simple" strstr implementation.
> There's significantly faster implementations available, but I doubt it's
> worth the effort as the version in this file only gets used if there is
> no system strstr.c.
Except that PR109306 says the new version is non-compliant and
is certainly slower than what we used to have. The only problem I see
on the old version (sure, it is not very fast version) is that for
strstr ("abcd", "") it returned "abcd"+4 rather than "abcd" because
strchr in that case changed p to point to the last character and then
strncmp returned 0.
The question reported in PR109306 is whether memcmp is required not to
access characters beyond the first difference or not.
For all of memcmp/strcmp/strncmp, C17 says:
"The sign of a nonzero value returned by the comparison functions memcmp,
strcmp, and strncmp
is determined by the sign of the difference between the values of the first
pair of characters (both
interpreted as unsigned char) that differ in the objects being compared."
but then in memcmp description says:
"The memcmp function compares the first n characters of the object pointed
to by s1 to the first n
characters of the object pointed to by s2."
rather than something similar to strncmp wording:
"The strncmp function compares not more than n characters (characters that
follow a null character
are not compared) from the array pointed to by s1 to the array pointed to
by
s2."
So, while for strncmp it seems clearly well defined when there is zero
terminator before reaching the n, for memcmp it is unclear if say
int
memcmp (const void *s1, const void *s2, size_t n)
{
int ret = 0;
size_t i;
const unsigned char *p1 = (const unsigned char *) s1;
const unsigned char *p2 = (const unsigned char *) s2;
for (i = n; i; i--)
if (p1[i - 1] != p2[i - 1])
ret = p1[i - 1] < p2[i - 1] ? -1 : 1;
return ret;
}
wouldn't be valid implementation (one which always compares all characters
and just returns non-zero from the first one that differs).
So, shouldn't we just revert and handle the len == 0 case correctly?
I think almost nothing really uses it, but still, the old version
at least worked nicer with a fast strchr.
Could as well strncmp (p + 1, s2 + 1, len - 1) if that is preferred
because strchr already compared the first character.
2023-04-02 Jakub Jelinek
PR other/109306
* strstr.c: Revert the 2020-11-13 changes.
(strstr): Return s1 if len is 0.
[Bug target/109374] FAIL: gnat.dg/div_zero.adb execution test
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109374 --- Comment #4 from dave.anglin at bell dot net --- On 2023-04-02 12:54 p.m., ebotcazou at gcc dot gnu.org wrote: >> I believe hppa-linux can unwind through signal frames. VDSO support was >> added fairly recently. > Does the unwinder compensate for the signal vs non-signal discrepancy? See > __gnat_adjust_context_for_raise in ada/init.c:470 for possible tweaks. I don't think it does with VDSO kernels. The unwinder uses MD_FALLBACK_FRAME_STATE_FOR with non VDSO kernels.
[Bug target/109078] Missing optimization on aarch64 for types like `float32x4x2_t`
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109078 Andrew Pinski changed: What|Removed |Added Severity|normal |enhancement
[Bug tree-optimization/109281] use std::optional results in suboptimal code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109281 Andrew Pinski changed: What|Removed |Added Severity|normal |enhancement
[Bug d/109377] New: FAIL: gdc.test/runnable/nan.d execution test
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109377 Bug ID: 109377 Summary: FAIL: gdc.test/runnable/nan.d execution test Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: d Assignee: ibuclaw at gdcproject dot org Reporter: danglin at gcc dot gnu.org Target Milestone: --- Host: hppa*-*-linux* Target: hppa*-*-linux* Build: hppa*-*-linux* Executing on host: /home/dave/gnu/gcc/objdir/gcc/testsuite/gdc/../../gdc -B/home/dave/gnu/gcc/objdir/gcc/testsuite/gdc/../../ runnable/nan.d -fdiagnostics-plain-output -I/home/dave/gnu/gcc/objdir/hppa-linux- gnu/./libphobos/libdruntime -I/home/dave/gnu/gcc/gcc/gcc/testsuite/../../libphobos/libdruntime -I/home/dave/gnu/gcc/gcc/gcc/testsuite/../../libphobos/src-Irunnable -B/home/dave/gnu/gcc/objdir/hppa-linux-gnu /./libphobos/src -L/home/dave/gnu/gcc/objdir/hppa-linux-gnu/./libphobos/src/.libs -lm -o ./nan.exe(timeout = 300) spawn -ignore SIGHUP /home/dave/gnu/gcc/objdir/gcc/testsuite/gdc/../../gdc -B/home/dave/gnu/gcc/objdir/gcc/testsuite/gdc/../../ runnable/nan.d -fdiagnostics-plain-output -I/home/dave/gnu/gcc/objdir/hppa-linux-gn u/./libphobos/libdruntime -I/home/dave/gnu/gcc/gcc/gcc/testsuite/../../libphobos/libdruntime -I/home/dave/gnu/gcc/gcc/gcc/testsuite/../../libphobos/src -Irunnable -B/home/dave/gnu/gcc/objdir/hppa-linux-gnu/./lib phobos/src -L/home/dave/gnu/gcc/objdir/hppa-linux-gnu/./libphobos/src/.libs -lm -o ./nan.exe PASS: gdc.test/runnable/nan.d (test for excess errors) Setting LD_LIBRARY_PATH to .:/home/dave/gnu/gcc/objdir/hppa-linux-gnu/./libphobos/src/.libs:/home/dave/gnu/gcc/objdir/gcc/testsuite/gdc/../..:.:/home/dave/gnu/gcc/objdir/hppa-linux-gnu/./libphobos/src/.libs:/hom e/dave/gnu/gcc/objdir/gcc/testsuite/gdc/../..:/home/dave/gnu/gcc/objdir/hppa-linux-gnu/libstdc++-v3/src/.libs:/home/dave/gnu/gcc/objdir/hppa-linux-gnu/libssp/.libs:/home/dave/gnu/gcc/objdir/hppa-linux-gnu/libpho bos/src/.libs:/home/dave/gnu/gcc/objdir/hppa-linux-gnu/libgm2/.libs:/home/dave/gnu/gcc/objdir/hppa-linux-gnu/libgomp/.libs:/home/dave/gnu/gcc/objdir/hppa-linux-gnu/libatomic/.libs:/home/dave/gnu/gcc/objdir/./gcc :/home/dave/gnu/gcc/objdir/./prev-gcc:/home/dave/gnu/gcc/objdir/hppa-linux-gnu/libstdc++-v3/src/.libs:/home/dave/gnu/gcc/objdir/hppa-linux-gnu/libssp/.libs:/home/dave/gnu/gcc/objdir/hppa-linux-gnu/libphobos/src/ .libs:/home/dave/gnu/gcc/objdir/hppa-linux-gnu/libgm2/.libs:/home/dave/gnu/gcc/objdir/hppa-linux-gnu/libgomp/.libs:/home/dave/gnu/gcc/objdir/hppa-linux-gnu/libatomic/.libs:/home/dave/gnu/gcc/objdir/./gcc:/home/d ave/gnu/gcc/objdir/./prev-gcc Execution timeout is: 300 spawn [open ...] core.exception.AssertError@runnable/nan.d(66): Assertion failure ../../../../gcc/libphobos/libdruntime/rt/dmain2.d:232 _d_traceContext [0x17daf] ../../../../gcc/libphobos/libdruntime/rt/deh.d:51 _d_createTrace [0x66e37] ../../../../gcc/libphobos/libdruntime/gcc/deh.d:484 _d_throw [0x489c7] ../../../../gcc/libphobos/libdruntime/core/exception.d:556 onAssertError [0x1e067] ../../../../gcc/libphobos/libdruntime/core/exception.d:785 _d_assertp [0x1e0af] ??:? void nan.test2!(float).test2() [0x1733b] ??:? _Dmain [0x171b3] FAIL: gdc.test/runnable/nan.d execution test and Executing on host: /home/dave/gnu/gcc/objdir/gcc/testsuite/gdc/../../gdc -B/home/dave/gnu/gcc/objdir/gcc/testsuite/gdc/../../ runnable/nan.d -fdiagnostics-plain-output -I/home/dave/gnu/gcc/objdir/hppa-linux- gnu/./libphobos/libdruntime -I/home/dave/gnu/gcc/gcc/gcc/testsuite/../../libphobos/libdruntime -I/home/dave/gnu/gcc/gcc/gcc/testsuite/../../libphobos/src -shared-libphobos -Irunnable -B/home/dave/gnu/gcc/obj dir/hppa-linux-gnu/./libphobos/src -L/home/dave/gnu/gcc/objdir/hppa-linux-gnu/./libphobos/src/.libs -lm -o ./nan.exe(timeout = 300) spawn -ignore SIGHUP /home/dave/gnu/gcc/objdir/gcc/testsuite/gdc/../../gdc -B/home/dave/gnu/gcc/objdir/gcc/testsuite/gdc/../../ runnable/nan.d -fdiagnostics-plain-output -I/home/dave/gnu/gcc/objdir/hppa-linux-gn u/./libphobos/libdruntime -I/home/dave/gnu/gcc/gcc/gcc/testsuite/../../libphobos/libdruntime -I/home/dave/gnu/gcc/gcc/gcc/testsuite/../../libphobos/src -shared-libphobos -Irunnable -B/home/dave/gnu/gcc/objdir/hp pa-linux-gnu/./libphobos/src -L/home/dave/gnu/gcc/objdir/hppa-linux-gnu/./libphobos/src/.libs -lm -o ./nan.exe PASS: gdc.test/runnable/nan.d -shared-libphobos (test for excess errors) Setting LD_LIBRARY_PATH to .:/home/dave/gnu/gcc/objdir/hppa-linux-gnu/./libphobos/src/.libs:/home/dave/gnu/gcc/objdir/gcc/testsuite/gdc/../..:.:/home/dave/gnu/gcc/objdir/hppa-linux-gnu/./libphobos/src/.libs:/hom e/dave/gnu/gcc/objdir/gcc/testsuite/gdc/../..:/home/dave/gnu/gcc/objdir/hppa-linux-gnu/libstdc++-v3/src/.libs:/home/dave/gnu/gcc/objdir/hppa-linux-gnu/libssp/.libs:/home/dave/gnu/gcc/objdir/hppa-linux-gnu/libpho
[Bug target/109374] FAIL: gnat.dg/div_zero.adb execution test
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109374 Eric Botcazou changed: What|Removed |Added Status|NEW |WAITING --- Comment #3 from Eric Botcazou --- > I believe hppa-linux can unwind through signal frames. VDSO support was > added fairly recently. Does the unwinder compensate for the signal vs non-signal discrepancy? See __gnat_adjust_context_for_raise in ada/init.c:470 for possible tweaks.
[Bug target/109374] FAIL: gnat.dg/div_zero.adb execution test
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109374 --- Comment #2 from dave.anglin at bell dot net --- I believe hppa-linux can unwind through signal frames. VDSO support was added fairly recently. The unwind tests in glibc all pass. GDB needs an update to unwind through signal frames with recent kernels.
[Bug target/109376] FAIL: gnat.dg/prot7.adb (test for excess errors)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109376 --- Comment #2 from dave.anglin at bell dot net --- I would judge the test should be skipped on hppa.
[Bug analyzer/109372] FAIL: gcc.dg/analyzer/pipe-glibc.c (test for excess errors)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109372 John David Anglin changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #2 from John David Anglin --- Likely. Fix for PR107396 was applied after update for latest build.
[Bug target/109376] FAIL: gnat.dg/prot7.adb (test for excess errors)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109376 Eric Botcazou changed: What|Removed |Added Ever confirmed|0 |1 Component|ada |target Status|UNCONFIRMED |WAITING CC||ebotcazou at gcc dot gnu.org Last reconfirmed||2023-04-02 --- Comment #1 from Eric Botcazou --- It needs to be skipped if the target does not support atomic primitives.
[Bug target/109375] FAIL: gnat.dg/opt39.adb scan-tree-dump-not optimized "tmp"
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109375 Eric Botcazou changed: What|Removed |Added Component|ada |target Last reconfirmed||2023-04-02 Status|UNCONFIRMED |WAITING Ever confirmed|0 |1 CC||ebotcazou at gcc dot gnu.org --- Comment #1 from Eric Botcazou --- See the dg-additional-option line in the test.
[Bug target/109374] FAIL: gnat.dg/div_zero.adb execution test
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109374 Eric Botcazou changed: What|Removed |Added Last reconfirmed||2023-04-02 Ever confirmed|0 |1 Status|UNCONFIRMED |NEW CC||ebotcazou at gcc dot gnu.org Component|ada |target --- Comment #1 from Eric Botcazou --- See the comment in the test.
[Bug analyzer/109372] FAIL: gcc.dg/analyzer/pipe-glibc.c (test for excess errors)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109372 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment #1 from Jakub Jelinek --- Dup of already fixed PR107396?
[Bug ada/109376] New: FAIL: gnat.dg/prot7.adb (test for excess errors)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109376 Bug ID: 109376 Summary: FAIL: gnat.dg/prot7.adb (test for excess errors) Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: ada Assignee: unassigned at gcc dot gnu.org Reporter: danglin at gcc dot gnu.org CC: dkm at gcc dot gnu.org Target Milestone: --- Host: hppa*-*-linux* Target: hppa*-*-linux* Build: hppa*-*-linux* Executing on host: /home/dave/gnu/gcc/objdir/gcc/gnatmake --GCC=/home/dave/gnu/gcc/objdir/gcc/xgcc --GNATBIND=/home/dave/gnu/gcc/objdir/gcc/gnatbind --GNATLINK=/home/dave/gnu/gcc/objdir/gcc/gnatlink -cargs -B/ho me/dave/gnu/gcc/objdir/gcc -largs --GCC=/home/dave/gnu/gcc/objdir/gcc/xgcc\ -B/home/dave/gnu/gcc/objdir/gcc\ -margs --RTS=/home/dave/gnu/gcc/objdir/hppa-linux-gnu/./libada -q -f /home/dave/gnu/gcc/gcc/gcc/test suite/gnat.dg/prot7.adb -largs -margs -fdiagnostics-plain-output -gnatwa -gnatVa -c -u -S -o prot7.s(timeout = 300) spawn -ignore SIGHUP /home/dave/gnu/gcc/objdir/gcc/gnatmake --GCC=/home/dave/gnu/gcc/objdir/gcc/xgcc --GNATBIND=/home/dave/gnu/gcc/objdir/gcc/gnatbind --GNATLINK=/home/dave/gnu/gcc/objdir/gcc/gnatlink -cargs -B/ home/dave/gnu/gcc/objdir/gcc -largs --GCC=/home/dave/gnu/gcc/objdir/gcc/xgcc -B/home/dave/gnu/gcc/objdir/gcc -margs --RTS=/home/dave/gnu/gcc/objdir/hppa-linux-gnu/./libada -q -f /home/dave/gnu/gcc/gcc/gcc/tests uite/gnat.dg/prot7.adb -largs -margs -fdiagnostics-plain-output -gnatwa -gnatVa -c -u -S -o prot7.s prot7.adb:5:04: error: Lock_Free aspect requires target support for atomic primitives prot7.adb:6:07: error: illegal body when Lock_Free given prot7.adb:11:07: error: illegal body when Lock_Free given gnatmake: "/home/dave/gnu/gcc/gcc/gcc/testsuite/gnat.dg/prot7.adb" compilation error compiler exited with status 1 Executing on host: /home/dave/gnu/gcc/objdir/gcc/gnatclean -c -q -n prot7 (timeout = 300) spawn -ignore SIGHUP /home/dave/gnu/gcc/objdir/gcc/gnatclean -c -q -n prot7 FAIL: gnat.dg/prot7.adb (test for excess errors) Excess errors: prot7.adb:5:04: error: Lock_Free aspect requires target support for atomic primitives prot7.adb:6:07: error: illegal body when Lock_Free given prot7.adb:11:07: error: illegal body when Lock_Free given
[Bug fortran/103931] Type name "c_ptr" is ambiguous when iso_c_binding is imported both directly and indirectly
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103931 --- Comment #11 from Bernhard Reutner-Fischer --- (In reply to Bernhard Reutner-Fischer from comment #10) > (In reply to anlauf from comment #9) > > The reduced testcase compiles for me with today's 13-trunk, but not > > 12-branch. > > However, the full original testcase fails with varying errors depending on > > the > > gfortran version. > > Does the full testcase compile on trunk, with d7caf313525a, i assume? Both the original testcase as well as the reduced testcase from comment #2 compile fine for me with trunk from earlier today at r13-6974-g802ab7d0db5b5a
[Bug ada/109375] New: FAIL: gnat.dg/opt39.adb scan-tree-dump-not optimized "tmp"
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109375 Bug ID: 109375 Summary: FAIL: gnat.dg/opt39.adb scan-tree-dump-not optimized "tmp" Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: ada Assignee: unassigned at gcc dot gnu.org Reporter: danglin at gcc dot gnu.org CC: dkm at gcc dot gnu.org Target Milestone: --- Host: hppa*-*-linux* Target: hppa*-*-linux* Build: hppa*-*-linux* Executing on host: /home/dave/gnu/gcc/objdir/gcc/gnatmake --GCC=/home/dave/gnu/gcc/objdir/gcc/xgcc --GNATBIND=/home/dave/gnu/gcc/objdir/gcc/gnatbind --GNATLINK=/home/dave/gnu/gcc/objdir/gcc/gnatlink -cargs -B/home/dave/gnu/gcc/objdir/gcc -largs --GCC=/home/dave/gnu/gcc/objdir/gcc/xgcc\ -B/home/dave/gnu/gcc/objdir/gcc\ -margs --RTS=/home/dave/gnu/gcc/objdir/hppa-linux-gnu/./libada -q -f /home/dave/gnu/gcc/gcc/gcc/testsuite/gnat.dg/opt39.adb -largs -margs -fdiagnostics-plain-output -O2 -fno-inline -fdump-tree-optimized -c -u -S -o opt39.s(timeout = 300) spawn -ignore SIGHUP /home/dave/gnu/gcc/objdir/gcc/gnatmake --GCC=/home/dave/gnu/gcc/objdir/gcc/xgcc --GNATBIND=/home/dave/gnu/gcc/objdir/gcc/gnatbind --GNATLINK=/home/dave/gnu/gcc/objdir/gcc/gnatlink -cargs -B/home/dave/gnu/gcc/objdir/gcc -largs --GCC=/home/dave/gnu/gcc/objdir/gcc/xgcc -B/home/dave/gnu/gcc/objdir/gcc -margs --RTS=/home/dave/gnu/gcc/objdir/hppa-linux-gnu/./libada -q -f /home/dave/gnu/gcc/gcc/gcc/testsuite/gnat.dg/opt39.adb -largs -margs -fdiagnostics-plain-output -O2 -fno-inline -fdump-tree-optimized -c -u -S -o opt39.s Executing on host: /home/dave/gnu/gcc/objdir/gcc/gnatclean -c -q -n opt39 (timeout = 300) spawn -ignore SIGHUP /home/dave/gnu/gcc/objdir/gcc/gnatclean -c -q -n opt39 ./opt39.ali ./opt39.s PASS: gnat.dg/opt39.adb (test for excess errors) PASS: gnat.dg/opt39.adb scan-tree-dump-not optimized "MEM" FAIL: gnat.dg/opt39.adb scan-tree-dump-not optimized "tmp"
[Bug ada/109374] New: FAIL: gnat.dg/div_zero.adb execution test
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109374 Bug ID: 109374 Summary: FAIL: gnat.dg/div_zero.adb execution test Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: ada Assignee: unassigned at gcc dot gnu.org Reporter: danglin at gcc dot gnu.org CC: dkm at gcc dot gnu.org Target Milestone: --- Host: hppa*-*-linux* Target: hppa*-*-linux* Build: hppa*-*-linux* Executing on host: /home/dave/gnu/gcc/objdir/gcc/gnatmake --GCC=/home/dave/gnu/gcc/objdir/gcc/xgcc --GNATBIND=/home/dave/gnu/gcc/objdir/gcc/gnatbind --GNATLINK=/home/dave/gnu/gcc/objdir/gcc/gnatlink -cargs -B/ho me/dave/gnu/gcc/objdir/gcc -largs --GCC=/home/dave/gnu/gcc/objdir/gcc/xgcc\ -B/home/dave/gnu/gcc/objdir/gcc\ -margs --RTS=/home/dave/gnu/gcc/objdir/hppa-linux-gnu/./libada -q -f /home/dave/gnu/gcc/gcc/gcc/test suite/gnat.dg/div_zero.adb -largs -margs -fdiagnostics-plain-output -largs -lm -margs -o ./div_zero.exe(timeout = 300) spawn -ignore SIGHUP /home/dave/gnu/gcc/objdir/gcc/gnatmake --GCC=/home/dave/gnu/gcc/objdir/gcc/xgcc --GNATBIND=/home/dave/gnu/gcc/objdir/gcc/gnatbind --GNATLINK=/home/dave/gnu/gcc/objdir/gcc/gnatlink -cargs -B/ home/dave/gnu/gcc/objdir/gcc -largs --GCC=/home/dave/gnu/gcc/objdir/gcc/xgcc -B/home/dave/gnu/gcc/objdir/gcc -margs --RTS=/home/dave/gnu/gcc/objdir/hppa-linux-gnu/./libada -q -f /home/dave/gnu/gcc/gcc/gcc/tests uite/gnat.dg/div_zero.adb -largs -margs -fdiagnostics-plain-output -largs -lm -margs -o ./div_zero.exe Executing on host: /home/dave/gnu/gcc/objdir/gcc/gnatclean -c -q -n ./div_zero (timeout = 300) spawn -ignore SIGHUP /home/dave/gnu/gcc/objdir/gcc/gnatclean -c -q -n ./div_zero ./div_zero.ali ./div_zero.o PASS: gnat.dg/div_zero.adb (test for excess errors) Setting LD_LIBRARY_PATH to :/home/dave/gnu/gcc/objdir/gcc::/home/dave/gnu/gcc/objdir/gcc:/home/dave/gnu/gcc/objdir/hppa-linux-gnu/libstdc++-v3/src/.libs:/home/dave/gnu/gcc/objdir/hppa-linux-gnu/libssp/.libs:/hom e/dave/gnu/gcc/objdir/hppa-linux-gnu/libphobos/src/.libs:/home/dave/gnu/gcc/objdir/hppa-linux-gnu/libgm2/.libs:/home/dave/gnu/gcc/objdir/hppa-linux-gnu/libgomp/.libs:/home/dave/gnu/gcc/objdir/hppa-linux-gnu/liba tomic/.libs:/home/dave/gnu/gcc/objdir/./gcc:/home/dave/gnu/gcc/objdir/./prev-gcc:/home/dave/gnu/gcc/objdir/hppa-linux-gnu/libstdc++-v3/src/.libs:/home/dave/gnu/gcc/objdir/hppa-linux-gnu/libssp/.libs:/home/dave/g nu/gcc/objdir/hppa-linux-gnu/libphobos/src/.libs:/home/dave/gnu/gcc/objdir/hppa-linux-gnu/libgm2/.libs:/home/dave/gnu/gcc/objdir/hppa-linux-gnu/libgomp/.libs:/home/dave/gnu/gcc/objdir/hppa-linux-gnu/libatomic/.l ibs:/home/dave/gnu/gcc/objdir/./gcc:/home/dave/gnu/gcc/objdir/./prev-gcc Execution timeout is: 300 spawn [open ...] raised CONSTRAINT_ERROR : SIGFPE FAIL: gnat.dg/div_zero.adb execution test
[Bug testsuite/95706] New test case gfortran.dg/pr95690.f90 fails
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95706 --- Comment #14 from John David Anglin --- Executing on host: /home/dave/gnu/gcc/objdir/gcc/testsuite/gfortran/../../gfortran -B/home/dave/gnu/gcc/objdir/gcc/testsuite/gfortran/../../ -B/home/dave/gnu/gcc/objdir/hppa-linux-gnu/./libgfortran/ /home/dave/gnu/gcc/gcc/gcc/testsuite/gfortran.dg/pr95690.f90 -fdiagnostics-plain-output -fdiagnostics-plain-output-O -pedantic-errors -S -o pr95690.s(timeout = 300) spawn -ignore SIGHUP /home/dave/gnu/gcc/objdir/gcc/testsuite/gfortran/../../gfortran -B/home/dave/gnu/gcc/objdir/gcc/testsuite/gfortran/../../ -B/home/dave/gnu/gcc/objdir/hppa-linux-gnu/./libgfortran/ /home/dave/gnu/gcc/gcc/gcc/testsuite/gfortran.dg/pr95690.f90 -fdiagnostics-plain-output -fdiagnostics-plain-output -O -pedantic-errors -S -o pr95690.s /home/dave/gnu/gcc/gcc/gcc/testsuite/gfortran.dg/pr95690.f90:5:21: Error: initializer for floating value is not a floating constant compiler exited with status 1 FAIL: gfortran.dg/pr95690.f90 -O (test for errors, line 6) FAIL: gfortran.dg/pr95690.f90 -O (test for excess errors) Excess errors: /home/dave/gnu/gcc/gcc/gcc/testsuite/gfortran.dg/pr95690.f90:5:21: Error: initializer for floating value is not a floating constant
[Bug testsuite/94384] FAIL: gfortran.dg/fmt_f_default_field_width_3.f90 -O (test for excess errors)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94384 --- Comment #2 from John David Anglin --- Also: FAIL: gfortran.dg/fmt_g_default_field_width_3.f90 -O (test for errors, line 36)
[Bug libfortran/109373] New: remove --enable-intermodule from libgfortran configure
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109373 Bug ID: 109373 Summary: remove --enable-intermodule from libgfortran configure Product: gcc Version: unknown Status: UNCONFIRMED Severity: minor Priority: P3 Component: libfortran Assignee: unassigned at gcc dot gnu.org Reporter: aldot at gcc dot gnu.org Target Milestone: --- r0-103106-gde6ba7aee152a0 removed --enable-intermodule (in favour of LTO) but libgfortran still has it.
[Bug testsuite/94384] FAIL: gfortran.dg/fmt_f_default_field_width_3.f90 -O (test for excess errors)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94384 --- Comment #1 from John David Anglin --- Test still fails with version 13.0.1 20230330 but fail is different: Executing on host: /home/dave/gnu/gcc/objdir/gcc/testsuite/gfortran/../../gfortran -B/home/dave/gnu/gcc/objdir/gcc/testsuite/gfortran/../../ -B/home/dave/gnu/gcc/objdir/hppa-linux-gnu/./libgfortran/ /home/dave/gnu/gcc/gcc/gcc/testsuite/gfortran.dg/fmt_f_default_field_width_3.f90 -fdiagnostics-plain-output -fdiagnostics-plain-output-O -cpp -fdec -fno-dec-format-defaults -S -o fmt_f_default_field_width_3.s(timeout = 300) spawn -ignore SIGHUP /home/dave/gnu/gcc/objdir/gcc/testsuite/gfortran/../../gfortran -B/home/dave/gnu/gcc/objdir/gcc/testsuite/gfortran/../../ -B/home/dave/gnu/gcc/objdir/hppa-linux-gnu/./libgfortran/ /home/dave/gnu/gcc/gcc/gcc/testsuite/gfortran.dg/fmt_f_default_field_width_3.f90 -fdiagnostics-plain-output -fdiagnostics-plain-output -O -cpp -fdec -fno-dec-format-defaults -S -o fmt_f_default_field_width_3.s /home/dave/gnu/gcc/gcc/gcc/testsuite/gfortran.dg/fmt_f_default_field_width_3.f90:23:23: Error: Nonnegative width required in format string at (1) /home/dave/gnu/gcc/gcc/gcc/testsuite/gfortran.dg/fmt_f_default_field_width_3.f90:26:23: Error: Nonnegative width required in format string at (1) /home/dave/gnu/gcc/gcc/gcc/testsuite/gfortran.dg/fmt_f_default_field_width_3.f90:29:23: Error: Nonnegative width required in format string at (1) compiler exited with status 1 PASS: gfortran.dg/fmt_f_default_field_width_3.f90 -O (test for errors, line 23) PASS: gfortran.dg/fmt_f_default_field_width_3.f90 -O (test for errors, line 26) PASS: gfortran.dg/fmt_f_default_field_width_3.f90 -O (test for errors, line 29) FAIL: gfortran.dg/fmt_f_default_field_width_3.f90 -O (test for errors, line 33) PASS: gfortran.dg/fmt_f_default_field_width_3.f90 -O (test for excess errors)
[Bug sanitizer/56781] boostrap-asan failure: fixincl fails to link (missing -lasan)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56781 Bernhard Reutner-Fischer changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #6 from Bernhard Reutner-Fischer --- Fixed.
[Bug jit/66054] bootstrap comparison failure with --enable-host-shared
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66054 Bernhard Reutner-Fischer changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #4 from Bernhard Reutner-Fischer --- This issue was fixed some time ago, closing.
[Bug c++/98531] [modules] g++.dg/modules/xtreme-header-2_a.H etc. FAIL
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98531
--- Comment #18 from John David Anglin ---
Executing on host: /home/dave/gnu/gcc/objdir/gcc/testsuite/g++/../../xg++
-B/home/dave/gnu/gcc/objdir/gcc/testsuite/g++/../../
/home/dave/gnu/gcc/gcc/gcc/testsuite/g++.dg/modules/xtreme-header-2_a.H
-fdiagnostics-plain-output -nostdinc++
-I/home/dave/gnu/gcc/objdir/hppa-linux-gnu/libstdc++-v3/include/hppa-linux-gnu
-I/home/dave/gnu/gcc/objdir/hppa-linux-gnu/libstdc++-v3/include
-I/home/dave/gnu/gcc/gcc/libstdc++-v3/libsupc++
-I/home/dave/gnu/gcc/gcc/libstdc++-v3/include/backward
-I/home/dave/gnu/gcc/gcc/libstdc++-v3/testsuite/util -fmessage-length=0
-std=c++17 -pedantic-errors -Wno-long-long -fmodule-header -S -o
xtreme-header-2_a.s(timeout = 300)
spawn -ignore SIGHUP /home/dave/gnu/gcc/objdir/gcc/testsuite/g++/../../xg++
-B/home/dave/gnu/gcc/objdir/gcc/testsuite/g++/../../
/home/dave/gnu/gcc/gcc/gcc/testsuite/g++.dg/modules/xtreme-header-2_a.H
-fdiagnostics-plain-output -nostdinc++
-I/home/dave/gnu/gcc/objdir/hppa-linux-gnu/libstdc++-v3/include/hppa-linux-gnu
-I/home/dave/gnu/gcc/objdir/hppa-linux-gnu/libstdc++-v3/include
-I/home/dave/gnu/gcc/gcc/libstdc++-v3/libsupc++
-I/home/dave/gnu/gcc/gcc/libstdc++-v3/include/backward
-I/home/dave/gnu/gcc/gcc/libstdc++-v3/testsuite/util -fmessage-length=0
-std=c++17 -pedantic-errors -Wno-long-long -fmodule-header -S -o
xtreme-header-2_a.s
In file included from /usr/include/oneapi/tbb/partitioner.h:47,
from /usr/include/oneapi/tbb/parallel_for.h:27,
from /usr/include/tbb/parallel_for.h:17,
from
/home/dave/gnu/gcc/gcc-trunk/libstdc++-v3/include/pstl/parallel_backend_tbb.h:20,
from
/home/dave/gnu/gcc/gcc-trunk/libstdc++-v3/include/pstl/parallel_backend.h:20,
from
/home/dave/gnu/gcc/gcc-trunk/libstdc++-v3/include/pstl/algorithm_impl.h:22,
from
/home/dave/gnu/gcc/objdir/hppa-linux-gnu/libstdc++-v3/include/pstl/glue_execution_defs.h:50,
from
/home/dave/gnu/gcc/objdir/hppa-linux-gnu/libstdc++-v3/include/execution:34,
from
/home/dave/gnu/gcc/gcc/gcc/testsuite/g++.dg/modules/xtreme-header-2.h:4,
from
/home/dave/gnu/gcc/gcc/gcc/testsuite/g++.dg/modules/xtreme-header-2_a.H:4:
/usr/include/oneapi/tbb/task_group.h:465:11: error: 'template
tbb::detail::d1::task*
tbb::detail::d1::function_task::execute(tbb::detail::d1::execution_data&)'
references internal linkage entity 'template tbb::detail::d1::task*
tbb::detail::d2::{anonymous}::task_ptr_or_nullptr(F&&)'
/usr/include/oneapi/tbb/task_group.h:494:11: error: 'template
tbb::detail::d1::task*
tbb::detail::d1::function_stack_task::execute(tbb::detail::d1::execution_data&)'
references internal linkage entity 'template tbb::detail::d1::task*
tbb::detail::d2::{anonymous}::task_ptr_or_nullptr(F&&)'
/home/dave/gnu/gcc/gcc/gcc/testsuite/g++.dg/modules/xtreme-header-2_a.H: error:
failed to write compiled module: Bad file data
/home/dave/gnu/gcc/gcc/gcc/testsuite/g++.dg/modules/xtreme-header-2_a.H: note:
compiled module file is
'gcm.cache/./home/dave/gnu/gcc/gcc/gcc/testsuite/g++.dg/modules/xtreme-header-2_a.H.gcm'
compiler exited with status 1
FAIL: g++.dg/modules/xtreme-header-2_a.H -std=c++17 (test for excess errors)
Excess errors:
/usr/include/oneapi/tbb/task_group.h:465:11: error: 'template
tbb::detail::d1::task*
tbb::detail::d1::function_task::execute(tbb::detail::d1::execution_data&)'
references internal linkage entity 'template tbb::detail::d1::task*
tbb::detail::d2::{anonymous}::task_ptr_or_nullptr(F&&)'
/usr/include/oneapi/tbb/task_group.h:494:11: error: 'template
tbb::detail::d1::task*
tbb::detail::d1::function_stack_task::execute(tbb::detail::d1::execution_data&)'
references internal linkage entity 'template tbb::detail::d1::task*
tbb::detail::d2::{anonymous}::task_ptr_or_nullptr(F&&)'
/home/dave/gnu/gcc/gcc/gcc/testsuite/g++.dg/modules/xtreme-header-2_a.H: error:
failed to write compiled module: Bad file data
FAIL: g++.dg/modules/xtreme-header-2_a.H module-cmi
(gcm.cache/$srcdir/g++.dg/modules/xtreme-header-2_a.H.gcm)
Executing on host: /home/dave/gnu/gcc/objdir/gcc/testsuite/g++/../../xg++
-B/home/dave/gnu/gcc/objdir/gcc/testsuite/g++/../../
/home/dave/gnu/gcc/gcc/gcc/testsuite/g++.dg/modules/xtreme-header-2_b.C
-fdiagnostics-plain-output -nostdinc++
-I/home/dave/gnu/gcc/objdir/hppa-linux-gnu/libstdc++-v3/include/hppa-linux-gnu
-I/home/dave/gnu/gcc/objdir/hppa-linux-gnu/libstdc++-v3/include
-I/home/dave/gnu/gcc/gcc/libstdc++-v3/libsupc++
-I/home/dave/gnu/gcc/gcc/libstdc++-v3/include/backward
-I/home/dave/gnu/gcc/gcc/libstdc++-v3/testsuite/util -fmessage-length=0
-std=c++17 -pedantic-errors -Wno-long-long -fmodules-ts -fno-module-lazy -S -o
xtreme-header-2_b.s(timeout = 300)
spawn -ignore SIGHUP /home/dave/gnu/gcc/objdir/gcc/testsuite/g++/../../xg++
-B/home/dave/gnu/gcc/objdir/gcc/testsuite/g++/../../
[Bug analyzer/109372] New: FAIL: gcc.dg/analyzer/pipe-glibc.c (test for excess errors)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109372
Bug ID: 109372
Summary: FAIL: gcc.dg/analyzer/pipe-glibc.c (test for excess
errors)
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: analyzer
Assignee: dmalcolm at gcc dot gnu.org
Reporter: danglin at gcc dot gnu.org
Target Milestone: ---
Host: hppa*-*-linux*
Target: hppa*-*-linux*
Build: hppa*-*-linux*
spawn -ignore SIGHUP /home/dave/gnu/gcc/objdir/gcc/xgcc
-B/home/dave/gnu/gcc/objdir/gcc/
/home/dave/gnu/gcc/gcc/gcc/testsuite/gcc.dg/analyzer/pipe-glibc.c
-fdiagnostics-plain-output -fanalyzer -Wanalyzer-too-complex
-fanalyzer-call-summaries -S -o pipe-glibc.s
/home/dave/gnu/gcc/gcc/gcc/testsuite/gcc.dg/analyzer/pipe-glibc.c: In function
'write_to_pipe':
/home/dave/gnu/gcc/gcc/gcc/testsuite/gcc.dg/analyzer/pipe-glibc.c:28:3:
warning: use of possibly-NULL 'stream' where non-null expected [CWE-690]
[-Wanalyzer-possible-null-argument]
/home/dave/gnu/gcc/gcc/gcc/testsuite/gcc.dg/analyzer/pipe-glibc.c:27:12: note:
(1) this call could return NULL
/home/dave/gnu/gcc/gcc/gcc/testsuite/gcc.dg/analyzer/pipe-glibc.c:28:3: note:
(2) argument 4 ('stream') from (1) could be NULL where non-null expected
: note: argument 4 of '__builtin_fwrite' must be non-null
FAIL: gcc.dg/analyzer/pipe-glibc.c (test for excess errors)
Excess errors:
/home/dave/gnu/gcc/gcc/gcc/testsuite/gcc.dg/analyzer/pipe-glibc.c:28:3:
warning: use of possibly-NULL 'stream' where non-null expected [CWE-690]
[-Wanalyzer-possible-null-argument]
[Bug target/108722] gcc.dg/analyzer/file-CWE-1341-example.c fails on power 9 BE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108722 John David Anglin changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Target|powerpc64-linux-gnu |powerpc64-linux-gnu ||hppa-linux-gnu Last reconfirmed||2023-04-02 Host|powerpc64-linux-gnu |powerpc64-linux-gnu ||hppa-linux-gnu CC||danglin at gcc dot gnu.org Build|powerpc64-linux-gnu |powerpc64-linux-gnu ||hppa-linux-gnu
[Bug c++/98531] [modules] g++.dg/modules/xtreme-header-2_a.H etc. FAIL
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98531 John David Anglin changed: What|Removed |Added Target|i386-pc-solaris2.11,|i386-pc-solaris2.11, |sparc-sun-solaris2.11, |sparc-sun-solaris2.11, |i586-unknown-freebsd11.4, |i586-unknown-freebsd11.4, |x86_64-unknown-freebsd11.4, |x86_64-unknown-freebsd11.4, |*-*-darwin* |*-*-darwin* ||hppa-*-linux-gnu Last reconfirmed|2021-01-05 00:00:00 |2023-4-2 CC||danglin at gcc dot gnu.org --- Comment #17 from John David Anglin --- On hppa-unknown-linux-gnu with 13.0.1 20230330 (experimental): FAIL: g++.dg/modules/xtreme-header-2_a.H -std=c++17 (test for excess errors) FAIL: g++.dg/modules/xtreme-header-2_a.H -std=c++2a (test for excess errors) FAIL: g++.dg/modules/xtreme-header-2_a.H -std=c++2b (test for excess errors) FAIL: g++.dg/modules/xtreme-header-2_a.H module-cmi (gcm.cache/\$srcdir/g++.dg/modules/xtreme-header-2_a.H.gcm) FAIL: g++.dg/modules/xtreme-header-2_a.H module-cmi (gcm.cache/\$srcdir/g++.dg/modules/xtreme-header-2_a.H.gcm) FAIL: g++.dg/modules/xtreme-header-2_a.H module-cmi (gcm.cache/\$srcdir/g++.dg/modules/xtreme-header-2_a.H.gcm) FAIL: g++.dg/modules/xtreme-header-2_b.C -std=c++17 (test for excess errors) FAIL: g++.dg/modules/xtreme-header-2_b.C -std=c++2a (test for excess errors) FAIL: g++.dg/modules/xtreme-header-2_b.C -std=c++2b (test for excess errors) FAIL: g++.dg/modules/xtreme-header-2_c.C -std=c++17 (test for excess errors) FAIL: g++.dg/modules/xtreme-header-2_c.C -std=c++2a (test for excess errors) FAIL: g++.dg/modules/xtreme-header-2_c.C -std=c++2b (test for excess errors) FAIL: g++.dg/modules/xtreme-header-5_c.C -std=c++2a (test for excess errors) FAIL: g++.dg/modules/xtreme-header-5_c.C -std=c++2b (test for excess errors) FAIL: g++.dg/modules/xtreme-header_a.H -std=c++17 (test for excess errors) FAIL: g++.dg/modules/xtreme-header_a.H -std=c++2a (test for excess errors) FAIL: g++.dg/modules/xtreme-header_a.H -std=c++2b (test for excess errors) FAIL: g++.dg/modules/xtreme-header_a.H module-cmi (gcm.cache/\$srcdir/g++.dg/modules/xtreme-header_a.H.gcm) FAIL: g++.dg/modules/xtreme-header_a.H module-cmi (gcm.cache/\$srcdir/g++.dg/modules/xtreme-header_a.H.gcm) FAIL: g++.dg/modules/xtreme-header_a.H module-cmi (gcm.cache/\$srcdir/g++.dg/modules/xtreme-header_a.H.gcm) FAIL: g++.dg/modules/xtreme-header_b.C -std=c++17 (test for excess errors) FAIL: g++.dg/modules/xtreme-header_b.C -std=c++2a (test for excess errors) FAIL: g++.dg/modules/xtreme-header_b.C -std=c++2b (test for excess errors)
[Bug tree-optimization/109363] [13 Regression] gcc.dg/tree-ssa/pr23109.c cris-elf reciptmp with r13-6945-g429a7a88438cc8
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109363 Hans-Peter Nilsson changed: What|Removed |Added Target Milestone|--- |13.0 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Hans-Peter Nilsson --- Fixed by r13-6960-g1e1b30a6a49714 (had a typo in the bugzilla markup, so did not appear here).
