[Bug c++/98327] C++ Module ICE on Linux

2020-12-16 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98327 fdlbxtqi changed: What|Removed |Added CC||nathan at gcc dot gnu.org --- Comment #1 from

[Bug c++/98327] New: C++ Module ICE on Linux

2020-12-16 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98327 Bug ID: 98327 Summary: C++ Module ICE on Linux Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: un

[Bug bootstrap/98300] GCC 11 failed to build on Windows 10. I guess the new module completely breaks this.

2020-12-15 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98300 --- Comment #9 from fdlbxtqi --- (In reply to Nathan Sidwell from comment #6) > Created attachment 49769 [details] > potential patch > > Care to give this patch a try? hello??

[Bug bootstrap/98300] GCC 11 failed to build on Windows 10. I guess the new module completely breaks this.

2020-12-15 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98300 --- Comment #8 from fdlbxtqi --- (In reply to Nathan Sidwell from comment #6) > Created attachment 49769 [details] > potential patch > > Care to give this patch a try? make[2]: Leaving directory '/home/unlvs/mingw-gcc-mcf-gthread/src/build-x86_

[Bug bootstrap/98300] GCC 11 failed to build on Windows 10. I guess the new module completely breaks this.

2020-12-15 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98300 --- Comment #7 from fdlbxtqi --- (In reply to Nathan Sidwell from comment #6) > Created attachment 49769 [details] > potential patch > > Care to give this patch a try? I will help you. no problem. BTW. Welcome to join discord so I can show you

[Bug bootstrap/98300] GCC 11 failed to build on Windows 10. I guess the new module completely breaks this.

2020-12-15 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98300 --- Comment #5 from fdlbxtqi --- (In reply to Nathan Sidwell from comment #3) > Hm, I thought there was sufficient #ifing to prevent that ... BTW. I tried the example you showed on the GCC module webpage on Linux. It fails to compile. why? cqw

[Bug bootstrap/98300] GCC 11 failed to build on Windows 10. I guess the new module completely breaks this.

2020-12-15 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98300 --- Comment #4 from fdlbxtqi --- (In reply to Nathan Sidwell from comment #3) > Hm, I thought there was sufficient #ifing to prevent that ... Try the compiler I build before to guard against this.

[Bug bootstrap/98300] GCC 11 failed to build on Windows 10. I guess the new module completely breaks this.

2020-12-15 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98300 --- Comment #2 from fdlbxtqi --- Here was an older version (GCC11 20201204) that can be used for bootstrapping. Please, thank you for fixing this issue ASAP. https://bitbucket.org/ejsvifq_mabmip/mingw-gcc/src/master/

[Bug bootstrap/98300] GCC 11 failed to build on Windows 10. I guess the new module completely breaks this.

2020-12-15 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98300 fdlbxtqi changed: What|Removed |Added Target||x86_64-msys2-mingw-w64, |

[Bug bootstrap/98300] New: GCC 11 failed to build on Windows 10. I guess the new module completely breaks this.

2020-12-15 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98300 Bug ID: 98300 Summary: GCC 11 failed to build on Windows 10. I guess the new module completely breaks this. Product: gcc Version: 11.0 Status: UNCONFIRMED Sever

[Bug c++/98057] New: ICE when build clang

2020-11-29 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98057 Bug ID: 98057 Summary: ICE when build clang Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unass

[Bug bootstrap/97622] ubsan ' unterminated quote character ''' in format

2020-10-29 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97622 fdlbxtqi changed: What|Removed |Added Resolution|--- |INVALID Status|WAITING

[Bug bootstrap/97622] ubsan ' unterminated quote character ''' in format

2020-10-29 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97622 --- Comment #3 from fdlbxtqi --- (In reply to Jakub Jelinek from comment #1) > Why do you think it is a bug? > Yes, it prints the opening quote, then > while (deref_depth-- > 0) > pp_star (&pretty_name); > prints some * characters a

[Bug bootstrap/97622] ubsan ' unterminated quote character ''' in format

2020-10-29 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97622 --- Comment #2 from fdlbxtqi --- (In reply to Jakub Jelinek from comment #1) > Why do you think it is a bug? > Yes, it prints the opening quote, then > while (deref_depth-- > 0) > pp_star (&pretty_name); > prints some * characters a

[Bug bootstrap/97622] New: ubsan ' unterminated quote character ''' in format

2020-10-28 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97622 Bug ID: 97622 Summary: ubsan ' unterminated quote character ''' in format Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component

[Bug bootstrap/97550] libgcc ICE on x86_64-linux-gnu compiler hosted on msys2

2020-10-28 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97550 --- Comment #2 from fdlbxtqi --- cp/cp-lang.o c-family/stub-objc.o cp/call.o cp/class.o cp/constexpr.o cp/constraint.o cp/coroutines.o cp/cp-gimplify.o cp/cp-objcp-common.o cp/cp-ubsan.o cp/cvt.o cp/cxx-pretty-print.o cp/decl.o cp/decl2.o c

[Bug tree-optimization/97620] -fexec-charset=IBM16804 triggers ICE

2020-10-28 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97620 --- Comment #3 from fdlbxtqi --- (In reply to Martin Sebor from comment #2) > This is almost certainly caused by an incomplete charset, same as in pr82700. > > *** This bug has been marked as a duplicate of bug 82700 *** Then provide a better e

[Bug analyzer/97620] -fexec-charset=IBM16804 triggers ICE

2020-10-28 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97620 --- Comment #1 from fdlbxtqi --- Program: #include int main() { printf("Hello World %d\n",6); }

[Bug analyzer/97620] New: -fexec-charset=IBM16804 triggers ICE

2020-10-28 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97620 Bug ID: 97620 Summary: -fexec-charset=IBM16804 triggers ICE Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: analyzer

[Bug c++/97550] New: libgcc ICE on x86_64-linux-gnu compiler hosted on msys2

2020-10-23 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97550 Bug ID: 97550 Summary: libgcc ICE on x86_64-linux-gnu compiler hosted on msys2 Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priorit

[Bug bootstrap/97499] build dos cross compiler ICE

2020-10-19 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97499 --- Comment #1 from fdlbxtqi --- /gcc_dos_build/./gcc/xgcc -B/gcc_dos_build/./gcc/ -B/i586-pc-msdosdjgpp/i586-pc-msdosdjgpp/bin/ -B/i586-pc-msdosdjgpp/i586-pc-msdosdjgpp/lib/ -isystem /i586-pc-msdosdjgpp/i586-pc-msdosdjgpp/include -isystem /i586-

[Bug bootstrap/97499] New: build dos cross compiler ICE

2020-10-19 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97499 Bug ID: 97499 Summary: build dos cross compiler ICE Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap A

[Bug target/97481] GCC ice when build with RISCV on msys2

2020-10-19 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97481 --- Comment #5 from fdlbxtqi --- (In reply to Jim Wilson from comment #2) > riscv-unknown-linux-gnu is not a supported target. You must use either > riscv32-unknown-linux-gnu or riscv64-unknwon-linux-gnu. Both compilers > support both word size

[Bug target/97481] GCC ice when build with RISCV on msys2

2020-10-19 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97481 --- Comment #4 from fdlbxtqi --- (In reply to Jim Wilson from comment #2) > riscv-unknown-linux-gnu is not a supported target. You must use either > riscv32-unknown-linux-gnu or riscv64-unknwon-linux-gnu. Both compilers > support both word size

[Bug target/97481] GCC ice when build with RISCV on msys2

2020-10-19 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97481 --- Comment #3 from fdlbxtqi --- (In reply to Jim Wilson from comment #2) > riscv-unknown-linux-gnu is not a supported target. You must use either > riscv32-unknown-linux-gnu or riscv64-unknwon-linux-gnu. Both compilers > support both word size

[Bug bootstrap/97481] GCC ice when build with RISCV on msys2

2020-10-18 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97481 --- Comment #1 from fdlbxtqi --- Created attachment 49395 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49395&action=edit riscv ICE

[Bug bootstrap/97481] New: GCC ice when build with RISCV on msys2

2020-10-18 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97481 Bug ID: 97481 Summary: GCC ice when build with RISCV on msys2 Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap

[Bug sanitizer/97478] New: Cross Build from windows to linux. It looks like the sys/timeb.h header file does not exist in latest glibc any more

2020-10-18 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97478 Bug ID: 97478 Summary: Cross Build from windows to linux. It looks like the sys/timeb.h header file does not exist in latest glibc any more Product: gcc Version:

[Bug libstdc++/97465] cross build gcc with vtv enabled failed. Cannot find out headers in glibc why?

2020-10-16 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97465 --- Comment #3 from fdlbxtqi --- (In reply to Jonathan Wakely from comment #2) > e.g. what kind of cross build? We're not psychic. I try to build x86_64-linux-gnu to x86_64-linux-gnu lol since I do not want vtv to ruin my ABIs. However, after I

[Bug libstdc++/97465] New: cross build gcc with vtv enabled failed. Cannot find out headers in glibc why?

2020-10-16 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97465 Bug ID: 97465 Summary: cross build gcc with vtv enabled failed. Cannot find out headers in glibc why? Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: n

[Bug target/97437] builtins subcarry and addcarry still not generate the right code. Not get optimized to immediate value

2020-10-15 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97437 --- Comment #4 from fdlbxtqi --- (In reply to Jakub Jelinek from comment #1) > I don't see anything undesirable on that. The 0 aka %rax is used in 7 > different instructions later on besides the move, so either we just clear > %ecx (can't use xo

[Bug rtl-optimization/97437] New: builtins subcarry and addcarry still not generate the right code. Not get optimized to immediate value

2020-10-15 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97437 Bug ID: 97437 Summary: builtins subcarry and addcarry still not generate the right code. Not get optimized to immediate value Product: gcc Version: 11.0 Status: UNCONFIRM

[Bug target/97387] we are near 2021, add carry intrinsic still does the wrong thing and generates silly code.

2020-10-14 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97387 --- Comment #14 from fdlbxtqi --- (In reply to fdlbxtqi from comment #13) > https://godbolt.org/z/fqGrz1 > > After this patch, the assembly generated is much better now. However, it > still contains many optimization problems. > > The problem i

[Bug target/97387] we are near 2021, add carry intrinsic still does the wrong thing and generates silly code.

2020-10-14 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97387 --- Comment #13 from fdlbxtqi --- https://godbolt.org/z/fqGrz1 After this patch, the assembly generated is much better now. However, it still contains many optimization problems. The problem is the code like this. Let's just walk through the a

[Bug target/97387] we are near 2021, add carry intrinsic still does the wrong thing and generates silly code.

2020-10-14 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97387 --- Comment #12 from fdlbxtqi --- (In reply to CVS Commits from comment #11) > The master branch has been updated by Jakub Jelinek : > > https://gcc.gnu.org/g:06bec55e80d98419121f3998d98d969990a75b0b > > commit r11-3882-g06bec55e80d98419121f399

[Bug bootstrap/97409] riscv cross toolchain build fails

2020-10-13 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97409 --- Comment #4 from fdlbxtqi --- (In reply to Andrew Pinski from comment #3) > (In reply to fdlbxtqi from comment #2) > > (In reply to Andrew Pinski from comment #1) > > > Sounds like the binutils does not have the needed support for (32bit) > >

[Bug bootstrap/97409] riscv cross toolchain build fails

2020-10-13 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97409 --- Comment #2 from fdlbxtqi --- (In reply to Andrew Pinski from comment #1) > Sounds like the binutils does not have the needed support for (32bit) > multilib. so I should build binutils with --disable-multilib?

[Bug bootstrap/97409] New: riscv cross toolchain build fails

2020-10-13 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97409 Bug ID: 97409 Summary: riscv cross toolchain build fails Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap

[Bug target/97387] we are near 2021, add carry intrinsic still does the wrong thing and generates silly code.

2020-10-13 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97387 --- Comment #7 from fdlbxtqi --- (In reply to Jakub Jelinek from comment #6) > Trying 10, 17 -> 18: >10: r88:QI=ltu(flags:CCC,0) > REG_DEAD flags:CCC >17: {flags:CCC=cmp(r88:QI-0x1,r88:QI);clobber scratch;} > REG_DEAD r88:QI >

[Bug rtl-optimization/97387] we are near 2021, add carry intrinsic still does the wrong thing and generates silly code.

2020-10-12 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97387 --- Comment #3 from fdlbxtqi --- (In reply to Hongtao.liu from comment #2) > Same issue as PR93990? many of them. It has been reported similar bugs since 2015.

[Bug rtl-optimization/97387] we are near 2021, add carry intrinsic still does the wrong thing and generates silly code.

2020-10-12 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97387 --- Comment #1 from fdlbxtqi --- All these instructions generated by GCC are very very wrong. https://gcc.godbolt.org/z/asMrKv

[Bug rtl-optimization/97387] New: we are near 2021, add carry intrinsic still does the wrong thing and generates silly code.

2020-10-12 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97387 Bug ID: 97387 Summary: we are near 2021, add carry intrinsic still does the wrong thing and generates silly code. Product: gcc Version: 11.0 Status: UNCONFIRMED

[Bug c++/97284] New: internal compiler error: 'global_options' are modified in local context

2020-10-04 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97284 Bug ID: 97284 Summary: internal compiler error: 'global_options' are modified in local context Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal

[Bug bootstrap/97262] Build GCC fail: error: cast from 'const ana::region*' to 'long int' loses precision

2020-10-01 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97262 --- Comment #3 from fdlbxtqi --- Change the line of (long)m_region to this. Compile success. the type long just considered harmful hashval_t hash () const { return (binding_key::impl_hash () ^ reinterpret_cast(m_region)); }

[Bug bootstrap/97262] Build GCC fail: error: cast from 'const ana::region*' to 'long int' loses precision

2020-10-01 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97262 --- Comment #2 from fdlbxtqi --- Let's face it. std::size_t should be the default integer type in both C and C++. type like long should never EVER be used.

[Bug bootstrap/97262] rror: cast from 'const ana::region*' to 'long int' loses precision

2020-09-30 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97262 --- Comment #1 from fdlbxtqi --- You cannot cast pointer this way. How do you guys control your code quality now?

[Bug bootstrap/97262] New: rror: cast from 'const ana::region*' to 'long int' loses precision

2020-09-30 Thread euloanty at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97262 Bug ID: 97262 Summary: rror: cast from 'const ana::region*' to 'long int' loses precision Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal