[Bug middle-end/116885] Wrong functionality of vararg causes malfunction or crashes

2024-09-29 Thread noloader at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116885 Jeffrey Walton changed: What|Removed |Added CC||noloader at gmail dot com --- Comment

[Bug sanitizer/84508] Load of misaligned address using _mm_load_sd

2024-05-29 Thread noloader at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84508 --- Comment #23 from Jeffrey Walton --- (In reply to Peter Cordes from comment #22) > [...] > That instruction is useless and should never be used in asm except for > code-alignment reasons (1 byte longer than MOVLPS, same length as MOVSD, all >

[Bug driver/81358] libatomic not automatically linked with C11 code

2022-08-23 Thread noloader at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81358 --- Comment #13 from Jeffrey Walton --- Add a mee too. When using sanitizers, like -fsanitize=undefined, the compiler driver is not adding the necessary libraries to link the program. Ugh... https://github.com/weidai11/cryptopp/issues/1141#issue

[Bug rtl-optimization/106568] -freorder-blocks-algorithm appears to causes a crash in stable code, no way to disable it

2022-08-08 Thread noloader at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106568 --- Comment #20 from Jeffrey Walton --- Hi Andrew. I went through the list of options that are enabled at -O2 from [1]. I built the library with each option separately at "-DNDEBUG -g2 -O2 -fno-xxx". Here is the list of suspects. I seem to rec

[Bug rtl-optimization/106568] -freorder-blocks-algorithm appears to causes a crash in stable code, no way to disable it

2022-08-08 Thread noloader at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106568 --- Comment #19 from Jeffrey Walton --- Created attachment 53427 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53427&action=edit Test script to build library at -O2 with -fno-xxx Test script to build library at -O2 with -fno-xxx

[Bug rtl-optimization/106568] -freorder-blocks-algorithm appears to causes a crash in stable code, no way to disable it

2022-08-08 Thread noloader at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106568 --- Comment #18 from Jeffrey Walton --- (In reply to Andrew Pinski from comment #17) > The other thing to try is -fstack-reuse=none. No joy with -fstack-reuse=none. The crash is still present.

[Bug rtl-optimization/106568] -freorder-blocks-algorithm appears to causes a crash in stable code, no way to disable it

2022-08-08 Thread noloader at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106568 --- Comment #15 from Jeffrey Walton --- It looks like -fno-strict-aliasing cleared the crash. This is bad because I thought we did not violate aliasing rules. Let me try to find it.

[Bug rtl-optimization/106568] -freorder-blocks-algorithm appears to causes a crash in stable code, no way to disable it

2022-08-08 Thread noloader at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106568 --- Comment #14 from Jeffrey Walton --- (In reply to Jeffrey Walton from comment #13) > (In reply to Andrew Pinski from comment #12) > > Can you try -fno-reorder-blocks-and-partition adding to the options? > > This would not be the first time th

[Bug rtl-optimization/106568] -freorder-blocks-algorithm appears to causes a crash in stable code, no way to disable it

2022-08-08 Thread noloader at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106568 --- Comment #13 from Jeffrey Walton --- (In reply to Andrew Pinski from comment #12) > Can you try -fno-reorder-blocks-and-partition adding to the options? > This would not be the first time this option caused issues with EH. No joy with -fno-r

[Bug rtl-optimization/106568] -freorder-blocks-algorithm appears to causes a crash in stable code, no way to disable it

2022-08-08 Thread noloader at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106568 --- Comment #10 from Jeffrey Walton --- I'm not sure if this is helpful, but Valgrind is showing invalid reads in the unwind gear: $ valgrind ./cryptest.exe vv 51 ==27339== Memcheck, a memory error detector ==27339== Copyright (C) 2002-2022, an

[Bug rtl-optimization/106568] -freorder-blocks-algorithm appears to causes a crash in stable code, no way to disable it

2022-08-08 Thread noloader at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106568 --- Comment #9 from Jeffrey Walton --- (In reply to Andrew Pinski from comment #8) > (In reply to Jeffrey Walton from comment #7) > > Try putting a breakpoint on the following functions: > _Unwind_RaiseException > _Unwind_ForcedUnwind > _Unwind

[Bug rtl-optimization/106568] -freorder-blocks-algorithm appears to causes a crash in stable code, no way to disable it

2022-08-08 Thread noloader at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106568 --- Comment #7 from Jeffrey Walton --- (In reply to Andrew Pinski from comment #6) > >And the program does not take the exception path. Instead it segfaults. > > If I read the backtrace correctly, it is trying to resume an unwind because > it d

[Bug rtl-optimization/106568] -freorder-blocks-algorithm appears to causes a crash in stable code, no way to disable it

2022-08-08 Thread noloader at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106568 --- Comment #5 from Jeffrey Walton --- (In reply to Andrew Pinski from comment #3) > Though there might be an EH issue but there has not been an EH issue for a > long time . This is an interesting observation. The stack trace shows frame #0 is

[Bug c++/106568] New: -freorder-blocks-algorithm appears to causes a crash in stable code, no way to disable it

2022-08-08 Thread noloader at gmail dot com via Gcc-bugs
Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: noloader at gmail dot com Target Milestone: --- Hi Everyone, This is going to be a shitty bug report because we don't have a reproducer. We believe we

[Bug target/104455] Cannot select -march=armv7-a using GCC 11

2022-02-10 Thread noloader at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104455 Jeffrey Walton changed: What|Removed |Added Resolution|INVALID |FIXED --- Comment #4 from Jeffrey Walt

[Bug target/104455] Cannot select -march=armv7-a using GCC 11

2022-02-09 Thread noloader at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104455 --- Comment #2 from Jeffrey Walton --- (In reply to Richard Earnshaw from comment #1) > What's the configuration of the compiler? Eg, the output of gcc -v Thanks Richard. I set-up a Debian Qemu/Chroot for armhf. I can now duplicate the problem

[Bug c++/104455] New: Cannot select -march=armv7-a using GCC 11

2022-02-08 Thread noloader at gmail dot com via Gcc-bugs
++ Assignee: unassigned at gcc dot gnu.org Reporter: noloader at gmail dot com Target Milestone: --- Hi Everyone, We are trying to fix a compile problem Debian encountered on Sid [1,2]. The machine is armhf, but I don't have access to it. Sid is using GCC 11, but I am not

[Bug driver/103863] We need a warning for loss of no-exec stacks

2021-12-29 Thread noloader at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103863 --- Comment #2 from Jeffrey Walton --- (In reply to Andrew Pinski from comment #1) > I think the warning needs to be implemented in the linker rather than in GCC > because the linker is what decides if there are executable stacks are needed > or

[Bug c/103863] New: We need a warning for loss of no-exec stacks

2021-12-29 Thread noloader at gmail dot com via Gcc-bugs
: c Assignee: unassigned at gcc dot gnu.org Reporter: noloader at gmail dot com Target Milestone: --- Hello, This is a feature request. For targets that support no-exec stacks, we need a warning when GCC generates code or drives the linker with loss of no-exec stacks. The

[Bug target/96168] GCC support for Apple Silicon (Arm64) on macOS requested

2021-04-26 Thread noloader at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96168 Jeffrey Walton changed: What|Removed |Added CC||noloader at gmail dot com --- Comment

[Bug target/82735] _mm256_zeroupper does not invalidate previously computed registers

2021-04-24 Thread noloader at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82735 --- Comment #6 from Jeffrey Walton --- Add 9.3 to the know to fail list: $ gcc --version gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0 Copyright (C) 2019 Free Software Foundation, Inc.

[Bug target/82735] _mm256_zeroupper does not invalidate previously computed registers

2021-04-24 Thread noloader at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82735 --- Comment #5 from Jeffrey Walton --- I think we are seeing this bug in the field. We are catching lots of failed self tests as we test on multiple platforms, including Ubuntu 14 ERS and Ubuntu 16 LTS. The problem makes GCC 4.8.4 through 7.5 pr

[Bug c++/53431] C++ preprocessor ignores #pragma GCC diagnostic

2021-02-27 Thread noloader at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53431 --- Comment #40 from Jeffrey Walton --- Still a problem in 2021.

[Bug c++/98416] POWER8: SIGILL handler does not restart properly after signal using GCC 10.2.1

2020-12-21 Thread noloader at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98416 --- Comment #3 from Jeffrey Walton --- (In reply to Andrew Pinski from comment #2) > This is invalid. > The instruction which is failing is: > 9c: f0 00 02 d0 xxspltib vs0,0 > > Which is only valid in power9 and above. > You need to mark CP

[Bug c++/98416] POWER8: SIGILL handler does not restart properly after signal using GCC 10.2.1

2020-12-21 Thread noloader at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98416 --- Comment #1 from Jeffrey Walton --- Created attachment 49831 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49831&action=edit Disassembly of ppc_power9.o Created with 'objdump --disassemble ppc_power9.o | c++filt > ppc_power9.disass'.

[Bug c++/98416] New: POWER8: SIGILL handler does not restart properly after signal using GCC 10.2.1

2020-12-21 Thread noloader at gmail dot com via Gcc-bugs
: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: noloader at gmail dot com Target Milestone: --- Created attachment 49827 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49827&action=edit preprocessed ppc_pow

[Bug middle-end/93644] [10/11 Regression] spurious -Wreturn-local-addr with PHI of PHI

2020-12-16 Thread noloader at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93644 --- Comment #13 from Jeffrey Walton --- On Wed, Dec 16, 2020 at 9:05 PM eggert at cs dot ucla.edu wrote: > ... > (B) there's no way to shut off the false alarm, not even with '# pragma GCC > diagnostic ignored "-Wreturn-local-addr"'. https://gc

[Bug analyzer/95031] GCC 10 Analyzer and fatal error: Terminated signal terminated program cc1plus

2020-05-11 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95031 --- Comment #3 from Jeffrey Walton --- (In reply to David Malcolm from comment #2) > Please note that C++ isn't supported in the -fanalyzer implementation in GCC > 10. I hope to get it working for GCC 11 (but there's a lot of work to do). Oh, s

[Bug analyzer/95043] New: GCC 10 Analyzer and false positive on 'memcpy(dest, src, count);'

2020-05-10 Thread noloader at gmail dot com
ty: normal Priority: P3 Component: analyzer Assignee: dmalcolm at gcc dot gnu.org Reporter: noloader at gmail dot com Target Milestone: --- Created attachment 48500 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48500&action=edit Preprocessed source

[Bug analyzer/95039] New: GCC 10 Analyzer and ‘‘result_decl’ not supported by dump_expr

2020-05-10 Thread noloader at gmail dot com
Priority: P3 Component: analyzer Assignee: dmalcolm at gcc dot gnu.org Reporter: noloader at gmail dot com Target Milestone: --- Created attachment 48498 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48498&action=edit Preprocessed source file ecp

[Bug analyzer/95031] New: GCC 10 Analyzer and fatal error: Terminated signal terminated program cc1plus

2020-05-09 Thread noloader at gmail dot com
: normal Priority: P3 Component: analyzer Assignee: dmalcolm at gcc dot gnu.org Reporter: noloader at gmail dot com Target Milestone: --- Created attachment 48496 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48496&action=edit Preprocessed sour

[Bug other/91744] -fno-pie is not honored

2019-09-11 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91744 --- Comment #3 from Jeffrey Walton --- (In reply to Andrew Pinski from comment #2) > You want -no-pie; not -fno-pie. > -no-pie turns off the linking and -fno-pie just turns off the compiler > option. Thanks Andrew.

[Bug c/91744] -fno-pie is not honored

2019-09-11 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91744 --- Comment #1 from Jeffrey Walton --- My bad, this should have been included: $ lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 $ gcc --version gcc (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0 Copyrigh

[Bug c/91744] New: -fno-pie is not honored

2019-09-11 Thread noloader at gmail dot com
: unassigned at gcc dot gnu.org Reporter: noloader at gmail dot com Target Milestone: --- From Initial SUPERCOP Haswell results for round 2 (https://groups.google.com/a/list.nist.gov/d/msg/pqc-forum/kiMo-1jBwDI/KS8VtDwWAgAJ): $ cat x.c #include extern int thenumber(void); int

[Bug target/91481] POWER9 "DARN" RNG intrinsic produces repeated output

2019-08-20 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91481 --- Comment #3 from Jeffrey Walton --- Lloyd's finding can be confirmed on GCC135. For example, gcc135:~$ /opt/at12.0/bin/gcc -O3 -mcpu=power9 -m64 darn.c -o darn gcc135:~$ ./darn 9FBE0B8B6E861BD6 9FBE0B8B6E861BD6 9FBE0B8B6E8

[Bug c++/70413] Class template names in anonymous namespaces are not globally unique

2019-07-23 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70413 --- Comment #4 from Jeffrey Walton --- Bumping this. We ran into a similar issue in GCC 6.3.0 on ARM with -flto. openSUSE enabled LTO by default, so we added a test case for all platforms which support LTO (including Debian with its stale packag

[Bug c++/91066] New: GCC does not provide XOP functions through

2019-07-02 Thread noloader at gmail dot com
Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: noloader at gmail dot com Target Milestone: --- This is a tad bit unusual since we can use SSE2, SSE3, ..., AVX, AVX2 as expected. According to the GCC docs and -march=bdver1, the arch does enable XOP as

[Bug target/78782] [x86] _mm_loadu_si64 intrinsic missing

2019-01-09 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78782 --- Comment #1 from Jeffrey Walton --- Also documented in the Intel Intrinsics Guide at https://software.intel.com/sites/landingpage/IntrinsicsGuide/#text=_mm_loadu_si64. According to the guide, the intrinsic is the movq instruction.

[Bug target/49670] internal compiler error: in extract_insn, at recog.c:2104

2018-12-08 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49670 Jeffrey Walton changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug target/49670] internal compiler error: in extract_insn, at recog.c:2104

2018-12-08 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49670 --- Comment #12 from Jeffrey Walton --- (In reply to Arseny Solokha from comment #11) > I believe this is irrelevant by now. Yeah, no doubt. May as well close it.

[Bug target/88234] UBsan and runtime error: signed integer overflow using unsigned vector

2018-12-06 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88234 --- Comment #13 from Jeffrey Walton --- The issue is cleared in GCC 9 from DEC 08 2018. Our self tests pass where they formerly failed. The failures are the reason I wanted a diagnostic run with UBsan. On GCC110 and GCC112 with gcc-9 located at

[Bug target/88234] UBsan and runtime error: signed integer overflow using unsigned vector

2018-11-30 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88234 --- Comment #12 from Jeffrey Walton --- (In reply to Jakub Jelinek from comment #10) > Author: jakub > Date: Thu Nov 29 14:23:21 2018 > New Revision: 266619 > > URL: https://gcc.gnu.org/viewcvs?rev=266619&root=gcc&view=rev > Log: > PR targ

[Bug target/88234] UBsan and runtime error: signed integer overflow using unsigned vector

2018-11-29 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88234 --- Comment #8 from Jeffrey Walton --- (In reply to Segher Boessenkool from comment #4) > This is documented in the ELFv2 ABI, linked from > https://gcc.gnu.org/readings.html . > > ... > (The vec_vsx_st doesn't have to do with the problem btw.

[Bug sanitizer/88234] New: UBsan and runtime error: signed integer overflow using unsigned vector

2018-11-27 Thread noloader at gmail dot com
Priority: P3 Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: noloader at gmail dot com CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, marxin

[Bug target/88078] error: '__float128' was not declared in this scope on PowerPC

2018-11-27 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88078 --- Comment #3 from Jeffrey Walton --- (In reply to Jonathan Wakely from comment #2) > For GCC 8.2 using -std=c++14 instead of -std=gnu++14 will disable the > __float128 specializations, avoiding the problem of long double and > __float128 being

[Bug c++/88078] New: error: '__float128' was not declared in this scope on PowerPC

2018-11-18 Thread noloader at gmail dot com
ty: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: noloader at gmail dot com Target Milestone: --- I'm working on GCC112 from the compile farm. I'm having trouble compiling a program with the C++ compiler. $ cat test.

[Bug web/87190] Feedback on documentation for symbol visibility

2018-09-02 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87190 --- Comment #1 from Jeffrey Walton --- In case it is needed, here's the citation for "Remember the docs say all symbols are private (not some symbols)": https://gcc.gnu.org/onlinedocs/gcc/Code-Gen-Options.html: Set the default ELF image symbol

[Bug web/87190] New: Feedback on documentation for symbol visibility

2018-09-02 Thread noloader at gmail dot com
: web Assignee: unassigned at gcc dot gnu.org Reporter: noloader at gmail dot com Target Milestone: --- This is general feedback on symbol visibility documentation. I feel like the docs are lacking some important information and it makes a resulting shared object appear to not

[Bug target/71659] _xgetbv intrinsic missing

2018-06-18 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71659 --- Comment #3 from Jeffrey Walton --- (In reply to postmaster from comment #2) > Portability is one main reason to add missing intrinsics... with combination > of cpuid check and _xgetbv() we can cleanly check if AVX or MPX is available > at run

[Bug rtl-optimization/84753] GCC does not fold xxswapd followed by vperm

2018-03-10 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84753 --- Comment #7 from Jeffrey Walton --- (In reply to Bill Schmidt from comment #4) > ... > > The best performance will be achieved by writing this loop entirely using > inline asm code, with all data loaded/stored using lxvd2x and stxvd2x (no > s

[Bug rtl-optimization/84753] GCC does not fold xxswapd followed by vperm

2018-03-07 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84753 --- Comment #3 from Jeffrey Walton --- (In reply to Jeffrey Walton from comment #2) > (In reply to Bill Schmidt from comment #1) > > GCC 4.8.5 is out of service. This is fixed in all in-service versions of > > GCC (6.4 and later). > > Interesti

[Bug rtl-optimization/84753] GCC does not fold xxswapd followed by vperm

2018-03-07 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84753 --- Comment #2 from Jeffrey Walton --- (In reply to Bill Schmidt from comment #1) > GCC 4.8.5 is out of service. This is fixed in all in-service versions of > GCC (6.4 and later). Interesting. I'm seeing it in GCC 7.2.0. Are you certain of this

[Bug rtl-optimization/84753] New: GCC does not fold xxswapd followed by vperm

2018-03-07 Thread noloader at gmail dot com
-optimization Assignee: unassigned at gcc dot gnu.org Reporter: noloader at gmail dot com Target Milestone: --- I'm working on GCC112 from the compile farm. It is ppc64-le machine. It has both GCC 4.8.5 and GCC 7.2.0 installed. The issue is present on both. We are tryi

[Bug sanitizer/84508] Load of misaligned address using _mm_load_sd

2018-02-24 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84508 --- Comment #8 from Jeffrey Walton --- (In reply to Jeffrey Walton from comment #0) > According to Intel > (https://software.intel.com/sites/landingpage/IntrinsicsGuide), there are no > alignment requirements for _mm_load_sd, _mm_store_sd and _mm

[Bug sanitizer/84508] Load of misaligned address using _mm_load_sd

2018-02-21 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84508 --- Comment #1 from Jeffrey Walton --- __m128d is a tad bit cleaner. It does not require the casts. $ cat test.c #include int main(int argc, char* argv[]) { unsigned char t[16+1]; __m128d x = _mm_load_sd((const double *)(t+1)); _mm_store_

[Bug sanitizer/84508] New: Load of misaligned address using _mm_load_sd

2018-02-21 Thread noloader at gmail dot com
: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: noloader at gmail dot com CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, marxin at gcc dot gnu.org Target Milestone

[Bug sanitizer/83961] AddressSanitizer CHECK failed on Aarch64

2018-01-22 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83961 --- Comment #3 from Jeffrey Walton --- (In reply to Jakub Jelinek from comment #2) > AFAIK AArch64 has multiple configurable sizes of the virtual address space > and older GCCs like 6 was only supporting one of those sizes, not all of > them. > S

[Bug sanitizer/83961] AddressSanitizer CHECK failed on Aarch64

2018-01-21 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83961 --- Comment #1 from Jeffrey Walton --- It looks like it was reported to the Ubuntu folks at https://bugs.launchpad.net/ubuntu/+bug/1709727, but I could not find a GCC report. There is also a gcc-6 patch.

[Bug sanitizer/83961] New: AddressSanitizer CHECK failed on Aarch64

2018-01-21 Thread noloader at gmail dot com
: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: noloader at gmail dot com CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, marxin at gcc dot gnu.org Target Milestone: --- I&#

[Bug c++/82209] Compile error "X causes a section type conflict with Y" should provide more information

2017-12-18 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82209 --- Comment #7 from Jeffrey Walton --- (In reply to Eric Gallager from comment #6) > (In reply to Eric Gallager from comment #5) > > (In reply to Jeffrey Walton from comment #4) > > > This is kind of weird... When we tested with C++03 by adding -

[Bug other/79885] --with-build-sysroot= does not get honored throughout the build (fix-includes, CPP, CXXCPP, configure-stage2)

2017-11-10 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79885 Jeffrey Walton changed: What|Removed |Added CC||noloader at gmail dot com --- Comment

[Bug c++/67036] GCC does not warn of throwing destructors in C++11, even when they lack noexcept(false) and std::uncaught_exception

2017-09-28 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67036 --- Comment #4 from Jeffrey Walton --- (In reply to Jonathan Wakely from comment #3) > VC++ prints: > > main.cpp(7): warning C4297: 'useless::~useless': function assumed not to > throw an exception but does > main.cpp(7): note: destructor or dea

[Bug c++/82209] Compile error "X causes a section type conflict with Y" should provide more information

2017-09-17 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82209 --- Comment #4 from Jeffrey Walton --- This is kind of weird... When we tested with C++03 by adding -std=c++03, we got 4 more of them. The check-in of interest is https://github.com/weidai11/cryptopp/commit/7097546cfcf742cf. Is there really no w

[Bug c++/82209] Compile error "X causes a section type conflict with Y" should provide more information

2017-09-14 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82209 --- Comment #2 from Jeffrey Walton --- (In reply to Eric Gallager from comment #1) > Do you have a complete standalone testcase we could use to reproduce? Thanks Eric. We were not able to reduce it to a minimal test case. That was part of the p

[Bug c++/82209] New: Compile error "X causes a section type conflict with Y" should provide more information

2017-09-13 Thread noloader at gmail dot com
NCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: noloader at gmail dot com Target Milestone: --- We are catching a compile error under GCC 6.10 on AIX. The error is shown below. The diagnostic messag

[Bug target/82112] internal compiler error: in fold_convert_loc, at fold-const.c:2262

2017-09-12 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82112 --- Comment #4 from Jeffrey Walton --- Thank you very much Jakub.

[Bug c++/82112] New: internal compiler error: in fold_convert_loc, at fold-const.c:2262

2017-09-05 Thread noloader at gmail dot com
Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: noloader at gmail dot com Target Milestone: --- I'm working on GCC112 (gcc112.fsffrance.org on the compile farm). $ cat test.cxx #include typedef unsigned char byte; typedef v

[Bug target/67317] [x86] Silly code generation for _addcarry_u32/_addcarry_u64

2017-08-21 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67317 Jeffrey Walton changed: What|Removed |Added CC||noloader at gmail dot com --- Comment

[Bug sanitizer/78204] ‘no_sanitize’ attribute directive ignored [-Wattributes]

2017-05-21 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78204 --- Comment #4 from Jeffrey Walton --- (In reply to Martin Liška from comment #3) > As I'm reading the source code, there's no option to do that. > Apart from 'no_sanitize' attribute, GCC supports 'no_sanitize_undefined' > attribute (clang does n

[Bug target/80377] gcc: error: unrecognized command line option ‘-mavx512’; did you mean ‘-mavx512 ’?

2017-04-19 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80377 --- Comment #6 from Jeffrey Walton --- (In reply to David Malcolm from comment #5) > Likewise, I tried but failed to reproduce it. > > A hunch: given the "-march=native", is there a chance that this bug is > dependent on the precise CPU flags on

[Bug target/57202] Please make the intrinsics headers like immintrin.h be usable without compiler flags

2017-04-17 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57202 --- Comment #9 from Jeffrey Walton --- On Mon, Apr 17, 2017 at 11:04 AM, glisse at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57202 > > --- Comment #8 from Marc Glisse --- > (In reply to Jeffrey Walton from comment #7

[Bug target/57202] Please make the intrinsics headers like immintrin.h be usable without compiler flags

2017-04-17 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57202 --- Comment #7 from Jeffrey Walton --- Please forgive my ignorance... What was fixed? The problem statement is/was "Please make all headers for intrinsics be includable without special compiler flags." But it appears the intrinsics are not avail

[Bug target/80377] gcc: error: unrecognized command line option ‘-mavx512’; did you mean ‘-mavx512 ’?

2017-04-09 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80377 --- Comment #2 from Jeffrey Walton --- (In reply to David Malcolm from comment #1) > Thanks for filing this. > > Similar to PR c++/72786, and probably worked-around on trunk by r242965; > presumably has a specific root-cause though. Yes, thanks

[Bug c/80377] New: gcc: error: unrecognized command line option ‘-mavx512’; did you mean ‘-mavx512 ’?

2017-04-09 Thread noloader at gmail dot com
Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: noloader at gmail dot com Target Milestone: --- >From the low hanging fruit department... I stumbled upon this on Fedora 25 x86_64 with GCC 6.3.1. I'm actually

[Bug driver/79974] New: First line of file is printed with unrecognized -mtune x86 option

2017-03-09 Thread noloader at gmail dot com
Priority: P3 Component: driver Assignee: unassigned at gcc dot gnu.org Reporter: noloader at gmail dot com Target Milestone: --- I'm working on a VIA C7-D processor. GCC version is 5.4.0 from Ubuntu. I'm attempting to use GCC's -mtune=c

[Bug libstdc++/71809] compile llvm3.8.0 failed by the libstdc++ of gcc6.1.0

2017-01-07 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71809 --- Comment #6 from Jeffrey Walton --- (In reply to Jeffrey Walton from comment #5) > (In reply to sulit from comment #4) > > ok > > Sulit, I'm seeing the issue under Clang 3.5 on Ubuntu 16. Do you have a LLVM > bug report for this issue? Here'

[Bug libstdc++/71809] compile llvm3.8.0 failed by the libstdc++ of gcc6.1.0

2017-01-07 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71809 Jeffrey Walton changed: What|Removed |Added CC||noloader at gmail dot com --- Comment

[Bug libstdc++/79017] Old PowerMac G5, MacPorts GCC 5.4, C++11 and "std::log2 has not been declared"

2017-01-07 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79017 --- Comment #15 from Jeffrey Walton --- (In reply to Jonathan Wakely from comment #14) > OK, thanks. I'm not going to try to add declarations like the libc++ patch > does, as it looks like that would only be correct for Snow Leopard and not > ear

[Bug libstdc++/79017] Old PowerMac G5, MacPorts GCC 5.4, C++11 and "std::log2 has not been declared"

2017-01-07 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79017 --- Comment #13 from Jeffrey Walton --- (In reply to Jonathan Wakely from comment #12) > What's the error? My bad... $ cat test.cxx // #include long long llrint(double x); long long llrintf(float x); long long llrintl(long double x); long long

[Bug libstdc++/79017] Old PowerMac G5, MacPorts GCC 5.4, C++11 and "std::log2 has not been declared"

2017-01-07 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79017 --- Comment #11 from Jeffrey Walton --- > Does this C program compile and link on 10.4 and 10.5? > > long long llrint(double x); > long long llrintf(float x); > long long llrintl(long double x); > long long llround(double x); > long long llroun

[Bug libstdc++/79017] Old PowerMac G5, MacPorts GCC 5.4, C++11 and "std::log2 has not been declared"

2017-01-06 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79017 --- Comment #9 from Jeffrey Walton --- (In reply to Jonathan Wakely from comment #2) > (In reply to Jeffrey Walton from comment #0) > > test.cxx:53:21: error: 'llrint' was not declared in this scope > >llrint(0.0); > >

[Bug libstdc++/79017] Old PowerMac G5, MacPorts GCC 5.4, C++11 and "std::log2 has not been declared"

2017-01-06 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79017 --- Comment #8 from Jeffrey Walton --- > Wow, this is a surprising statistic (for me)... OS X 10.5 makes up 29.1% of > the MacPorts downloads. Its the largest percentage for the OS group. Confer, > http://stats.macports.neverpanic.de/os_statisti

[Bug libstdc++/79017] Old PowerMac G5, MacPorts GCC 5.4, C++11 and "std::log2 has not been declared"

2017-01-06 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79017 --- Comment #7 from Jeffrey Walton --- (In reply to Jeffrey Walton from comment #5) > (In reply to Jonathan Wakely from comment #2) > ... > > But OS X 10.5.8 is pretty old, and this might not be worth doing if it > > doesn't affect current versio

[Bug libstdc++/79017] Old PowerMac G5, MacPorts GCC 5.4, C++11 and "std::log2 has not been declared"

2017-01-06 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79017 --- Comment #5 from Jeffrey Walton --- (In reply to Jonathan Wakely from comment #2) > (In reply to Jeffrey Walton from comment #0) > ... ^ > > Because these six functions are missing we treat all C99 math functions as > mi

[Bug libstdc++/79017] Old PowerMac G5, MacPorts GCC 5.4, C++11 and "std::log2 has not been declared"

2017-01-06 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79017 --- Comment #4 from Jeffrey Walton --- (In reply to Jonathan Wakely from comment #3) > Jeffrey, could you please add the output of '/opt/local/bin/g++-mp-5 > -dumpmachine' to the Target field of this bug report? Thanks. $ /opt/local/bin/g++-mp

[Bug libstdc++/79017] Old PowerMac G5, MacPorts GCC 5.4, C++11 and "std::log2 has not been declared"

2017-01-06 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79017 --- Comment #1 from Jeffrey Walton --- Also see Issue 53226 in the MacPorts issue tracker. "gcc5 @5.4: error: 'std::log2' has not been declared", https://trac.macports.org/ticket/53226.

[Bug libstdc++/79017] New: Old PowerMac G5, MacPorts GCC 5.4, C++11 and "std::log2 has not been declared"

2017-01-06 Thread noloader at gmail dot com
Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: noloader at gmail dot com Target Milestone: --- I'm working on a PowerMac G5. It runs OS X 10.5.8. It has MacPorts installed for updated gear. The

[Bug target/71767] Endless stream of warnings when using GCC with -Wa,-q and Clang Integrated Assembler

2016-09-14 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71767 --- Comment #10 from Jeffrey Walton --- > than adjusting section definitions - we need to change which ones are >> > selected in config/darwin.c >> > >> I _think_ you can detect which linker at runtime with something like the >> following: >> >>

[Bug target/71767] Endless stream of warnings when using GCC with -Wa,-q and Clang Integrated Assembler

2016-09-14 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71767 --- Comment #8 from Jeffrey Walton --- (In reply to Iain Sandoe from comment #7) > (In reply to Dominique d'Humieres from comment #4) > > I see the problem after having updated to Xcode 8.0. I am currently testing > > the following patch > > >

[Bug target/71767] Endless stream of warnings when using GCC with -Wa,-q and Clang Integrated Assembler

2016-09-14 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71767 --- Comment #5 from Jeffrey Walton --- (In reply to Dominique d'Humieres from comment #4) > I see the problem after having updated to Xcode 8.0. I am currently testing > the following patch > Just an FYI... Clang 3.7 and below do not witness th

[Bug target/72758] GCC 4.9.2 on Aarch64 missing vreinterpretq_u64_p128 and friends

2016-07-29 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72758 --- Comment #3 from Jeffrey Walton --- (In reply to Andrew Pinski from comment #2) > Note the testcase is wrong (but only slightly). Oh, you're right, thanks. That code was tested on the RPI3 to ensure it compiled as expected under Aarch32. Usi

[Bug target/72758] New: GCC 4.9.2 on Aarch64 missing vreinterpretq_u64_p128 and friends

2016-07-29 Thread noloader at gmail dot com
Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: noloader at gmail dot com Target Milestone: --- Created attachment 39035 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=39035&action=edit Preprocessed test.cc I'm

[Bug target/72738] internal compiler error: in expand_shift_1, at expmed.c:2318

2016-07-28 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72738 --- Comment #3 from Jeffrey Walton --- (In reply to Jeffrey Walton from comment #2) > (In reply to James Greenhalgh from comment #1) > > Testcase needs a #include to compile, but otherwise confirmed > > from GCC 4.9 through to trunk. > > > > No

[Bug target/72738] internal compiler error: in expand_shift_1, at expmed.c:2318

2016-07-28 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72738 --- Comment #2 from Jeffrey Walton --- (In reply to James Greenhalgh from comment #1) > Testcase needs a #include to compile, but otherwise confirmed > from GCC 4.9 through to trunk. > > Note that it isn't immediately clear that this is valid c

[Bug target/72736] warning: switch -mcpu=cortex-a53 conflicts with -march=armv8-a switch

2016-07-28 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72736 --- Comment #6 from Jeffrey Walton --- (In reply to James Greenhalgh from comment #5) > (In reply to Jeffrey Walton from comment #4) > > Thanks, and sorry to waste your time with it. > > > > Before I spin up another report that wastes a lot time

[Bug target/72738] New: internal compiler error: in expand_shift_1, at expmed.c:2318

2016-07-28 Thread noloader at gmail dot com
Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: noloader at gmail dot com Target Milestone: --- Created attachment 39027 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=39027&action=edit Preprocessed source file. Raspber

[Bug target/72736] warning: switch -mcpu=cortex-a53 conflicts with -march=armv8-a switch

2016-07-28 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72736 --- Comment #4 from Jeffrey Walton --- Thanks, and sorry to waste your time with it. Before I spin up another report that wastes a lot time, does this look like another issue with me (likely), or an issue with GCC (unlikely): internal compiler

[Bug driver/70132] ARM -mcpu=native can cause a double free abort.

2016-07-28 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70132 --- Comment #14 from Jeffrey Walton --- (In reply to ktkachov from comment #8) > Fixed on trunk for now. > Will backport after some time to the branches Bump... I don't think this has made it into Debian's 4.9.2-10.

[Bug driver/70132] ARM -mcpu=native can cause a double free abort.

2016-07-28 Thread noloader at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70132 Jeffrey Walton changed: What|Removed |Added CC||noloader at gmail dot com --- Comment

[Bug target/72737] New: warning: switch -mcpu=cortex-a53 conflicts with -march=armv8-a switch

2016-07-28 Thread noloader at gmail dot com
Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: noloader at gmail dot com Target Milestone: --- This looks like an issue similar to http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57907. It also appears similar to http

  1   2   3   >