[Bug c++/35876] Exceptions not working on FreeBSD

2008-04-18 Thread yuri at tsoft dot com
--- Comment #3 from yuri at tsoft dot com 2008-04-18 23:30 --- Closing it completely -- yuri at tsoft dot com changed: What|Removed |Added Status|RESOLVED

[Bug c++/35876] Exceptions not working on FreeBSD

2008-04-18 Thread yuri at tsoft dot com
--- Comment #2 from yuri at tsoft dot com 2008-04-18 23:29 --- Problem was because of the mixup of gcc libaries. Executable was built with one compiler and during the run different shared libraries were used. -- yuri at tsoft dot com changed: What|Removed

[Bug c++/35876] Exceptions not working on FreeBSD

2008-04-18 Thread yuri at tsoft dot com
--- Comment #4 from yuri at tsoft dot com 2008-04-19 01:07 --- Reopening this PR. Same testcase with gcc-4.3.0 on FreeBSD-7.0-STABLE aborts: Abort trap: 6 ldd output: libstdc++.so.6 => /usr/local/gcc/4.3.0/lib/libstdc++.so.6 (0x2807d000) libm.so.5 => /lib/lib

[Bug c++/35876] Exceptions not working on FreeBSD

2008-04-18 Thread yuri at tsoft dot com
--- Comment #5 from yuri at tsoft dot com 2008-04-19 01:09 --- The only broken version is 4.3.0, all 4.2.X throw exceptions ok. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35876

[Bug c++/36483] New: Getting an address of a byte-aligned field declared as a bit-field should be allowed

2008-06-10 Thread yuri at tsoft dot com
normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: yuri at tsoft dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36483

[Bug c++/25986] New: return from funcrtion of void value allowed

2006-01-26 Thread yuri at tsoft dot com
value allowed Product: gcc Version: 4.0.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: yuri at tsoft dot com http://gcc.gnu.org/bugzilla

[Bug c++/25986] return from funcrtion of void value allowed

2006-01-26 Thread yuri at tsoft dot com
--- Comment #2 from yuri at tsoft dot com 2006-01-27 00:02 --- > This functionality was *added* on > purpose to allow generic codes to be written seamlessly Sure! Then code "void f() { void x; retrun (x); }" should work. But it produces: t.C: In function `void f()'

[Bug c++/25986] return from funcrtion of void value allowed

2006-01-26 Thread yuri at tsoft dot com
--- Comment #4 from yuri at tsoft dot com 2006-01-27 00:44 --- For templates it's sufficient to treat void as type in template specializations. No need to further change language. Especially because generic programming doesn't really scale much beyond it's 'lo

[Bug c++/25986] return from funcrtion of void value allowed

2006-01-26 Thread yuri at tsoft dot com
--- Comment #8 from yuri at tsoft dot com 2006-01-27 03:09 --- > Let's close this PR as we do not have place for trolls. I am basing my opinion on the very practical experience w/out any intent of trolling. You either provide an example of wide-range successful GP use or take b

[Bug c++/25986] return from funcrtion of void value allowed

2006-01-26 Thread yuri at tsoft dot com
--- Comment #10 from yuri at tsoft dot com 2006-01-27 03:19 --- I never advocated C. I only noted that language was unreasonably changed to simplify few GP tricks. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25986

[Bug c++/17332] [3.4 Regression] Missed inline opportunity

2006-02-28 Thread yuri at tsoft dot com
--- Comment #5 from yuri at tsoft dot com 2006-02-28 09:53 --- So there should be no performance-related bugs reported any more since you only care about correctness? This IS a performance-related problem in gcc. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17332

[Bug c++/21560] New: #pragma(1) doesn't work on the inner classes inside the temlated class

2005-05-13 Thread yuri at tsoft dot com
temlated class Product: gcc Version: 3.4.3 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: yuri at tsoft dot com CC: gcc-bugs at gcc dot g

[Bug c++/21612] New: Strange symbols printed all over the error messages

2005-05-16 Thread yuri at tsoft dot com
4.0.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: yuri at tsoft dot com CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.c

[Bug c++/21614] New: invokation of undefined class'es method is ignored

2005-05-16 Thread yuri at tsoft dot com
s'es method is ignored Product: gcc Version: 4.0.0 Status: UNCONFIRMED Severity: critical Priority: P2 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: yuri at tsoft dot com CC: gcc-bugs at

[Bug c++/21614] [4.0/4.1 Regression] invokation of undefined class'es method is ignored

2005-05-17 Thread yuri at tsoft dot com
--- Additional Comments From yuri at tsoft dot com 2005-05-17 17:38 --- (In reply to comment #1) > Hmm, I think we get an error mark node but no error. Why is this the wrong code? It's easy to execute it. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21614

[Bug c++/19661] New: many redundant atexit calls emitted into the executable for static objects with empty destructors

2005-01-27 Thread yuri at tsoft dot com
When some object having empty destructor is declared as static in the local context of some function g++ still inserts call with the empty handler like <__tcf_0> below. It may seem like minor issue but redundant instructions increase chances for I-cache misses and worthen processor pipeline. Yur

[Bug c++/19661] unnecessary atexit calls emitted for static objects with empty destructors

2005-01-27 Thread yuri at tsoft dot com
--- Additional Comments From yuri at tsoft dot com 2005-01-28 01:26 --- (In reply to comment #1) > Confirmed, although I consider this to be a rather minor point since > the code is actually run only once. Here's a small test: I agree, but it bloats the code, therefo

[Bug c++/19662] New: [FEATURE REQUEST] Need an option preventing any atexit object destructions

2005-01-27 Thread yuri at tsoft dot com
Status: UNCONFIRMED Severity: normal Priority: P2 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: yuri at tsoft dot com CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19662

[Bug c++/19662] [FEATURE REQUEST] Need an option preventing any atexit object destructions

2005-01-28 Thread yuri at tsoft dot com
--- Additional Comments From yuri at tsoft dot com 2005-01-28 20:54 --- > If your objects are simple and do not need destruction, just don't > define destructors. > > -- Gaby Disagree, it may only be determined after the optimization that destructor is actuall empty.

[Bug rtl-optimization/19702] New: suboptimal multiple branch comparison code produced

2005-01-29 Thread yuri at tsoft dot com
ranch comparison code produced Product: gcc Version: 3.4.2 Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: rtl-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: yuri at tsoft dot co

[Bug rtl-optimization/19719] New: missed optimization on boolean operation with boolean arguments

2005-01-30 Thread yuri at tsoft dot com
Product: gcc Version: 3.4.2 Status: UNCONFIRMED Severity: normal Priority: P2 Component: rtl-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: yuri at tsoft dot com CC: gcc-bugs at gcc dot gnu dot org http:

[Bug rtl-optimization/19719] missed optimization on boolean operation with boolean arguments

2005-01-30 Thread yuri at tsoft dot com
--- Additional Comments From yuri at tsoft dot com 2005-01-31 06:16 --- Ooops, sorry, should be 2 instructions instead of 7 (3.5X inefficiency) should be pushl %ebp movl%esp, %ebp >movl8(%ebp), %eax >andl12(%ebp), %eax .p

[Bug tree-optimization/19726] New: suboptimal constructor generated

2005-01-31 Thread yuri at tsoft dot com
gnu dot org ReportedBy: yuri at tsoft dot com CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19726

[Bug target/19726] suboptimal constructor generated

2005-01-31 Thread yuri at tsoft dot com
--- Additional Comments From yuri at tsoft dot com 2005-01-31 22:02 --- actually I want to generalize it: any situation in C++/C/Ada when many enough close (in memory) variables are assigned the same value should use bulk "stos(b/w/l)". This should be applied as part of op

[Bug c++/19748] New: aggressive no-inline options still cause inlining

2005-02-01 Thread yuri at tsoft dot com
Priority: P2 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: yuri at tsoft dot com CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19748

[Bug c++/19748] aggressive no-inline options still cause inlining

2005-02-01 Thread yuri at tsoft dot com
--- Additional Comments From yuri at tsoft dot com 2005-02-02 02:07 --- (In reply to comment #2) > Also note sometimes when a function is pure/const it can be removed which is why it might act as > inlining. > > Do you have a simple example? > ... > Also note sometim

[Bug rtl-optimization/19943] New: missed optimization: memcpy is invoked with small size known upfront if invoked through inlined function(s)

2005-02-13 Thread yuri at tsoft dot com
AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: yuri at tsoft dot com CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19943

[Bug c++/19947] New: __attribute__ ((__always_inline__)) fails for no apparent reason

2005-02-13 Thread yuri at tsoft dot com
Product: gcc Version: 3.4.3 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: yuri at tsoft dot com CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19947

[Bug fortran/100662] New: intrinsic::ieee_arithmetic fails on aarch, powerpc architectures on FreeBSD

2021-05-18 Thread yuri at tsoft dot com via Gcc-bugs
: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: yuri at tsoft dot com Target Milestone: --- Fortran codes using intrinsic::ieee_arithmetic on aarch, powerpc architectures fail to compile. See details in this

[Bug fortran/100662] intrinsic::ieee_arithmetic fails on aarch, powerpc architectures on FreeBSD

2021-05-18 Thread yuri at tsoft dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100662 --- Comment #2 from Yuri --- intrinsic::ieee_arithmetic works fine on amd64/i386 architectures on the same OS. What do you think is missing/wrong in the OS that causes it?

[Bug fortran/100662] intrinsic::ieee_arithmetic fails on aarch, powerpc architectures on FreeBSD

2021-05-18 Thread yuri at tsoft dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100662 --- Comment #3 from Yuri --- On amd64 gcc installs the file finclude/ieee_arithmetic.mod and on aarch64 this file isn't installed. What is installed is defined by the gcc build process.

[Bug fortran/100662] intrinsic::ieee_arithmetic fails on aarch, powerpc architectures on FreeBSD

2021-05-18 Thread yuri at tsoft dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100662 --- Comment #5 from Yuri --- config.log doesn't contain the IEEE string even on amd64. libgfortran/configure.host seems to only enable IEEE modules on i?86 | x86_64 architectures through this code: > case "${host_cpu}" in > i?86 | x86_64) >

[Bug fortran/100662] intrinsic::ieee_arithmetic fails on aarch, powerpc architectures on FreeBSD

2021-05-18 Thread yuri at tsoft dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100662 --- Comment #7 from Yuri --- fpu-387.h is in the gcc10 source tree: > $ find . -name "fpu-*" > ./work/gcc-10.3.0/libgfortran/config/fpu-generic.h > ./work/gcc-10.3.0/libgfortran/config/fpu-sysv.h > ./work/gcc-10.3.0/libgfortran/config/fpu-glibc.

[Bug other/106328] New: Build doesn't respect -j N flag

2022-07-16 Thread yuri at tsoft dot com via Gcc-bugs
other Assignee: unassigned at gcc dot gnu.org Reporter: yuri at tsoft dot com Target Milestone: --- -j8 is given to it, but it creates ~130 lto1 processes. See this downstream issues for details: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265254

[Bug c++/110746] New: gcc-12 fails: sorry, unimplemented: PCH allocation failure

2023-07-19 Thread yuri at tsoft dot com via Gcc-bugs
Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: yuri at tsoft dot com Target Milestone: --- > : sorry, unimplemented: PCH allocation failure This message is in the GCC source code. What does this mean "PCH allocation failure&q

[Bug c++/110746] gcc-12 fails: sorry, unimplemented: PCH allocation failure

2023-07-19 Thread yuri at tsoft dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110746 --- Comment #1 from Yuri --- OS: FreeBSD 13.2

[Bug c++/110746] gcc-12 fails: sorry, unimplemented: PCH allocation failure

2023-07-19 Thread yuri at tsoft dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110746 --- Comment #4 from Yuri --- This happens during the build of the Ossia Score project: https://github.com/ossia/score

[Bug c++/110746] gcc-12 fails: sorry, unimplemented: PCH allocation failure

2023-07-19 Thread yuri at tsoft dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110746 --- Comment #6 from Yuri --- FAILED: src/plugins/score-plugin-avnd/CMakeFiles/score_plugin_avnd.dir/__/__/__/midiscaler_avnd.cpp.o /usr/local/libexec/ccache/g++13 -DBOOST_ASIO_DISABLE_CONCEPTS=1 -DBOOST_MATH_DISABLE_FLOAT128=1 -DBOOST_NO_RTTI=

[Bug c++/110746] gcc-12 fails: sorry, unimplemented: PCH allocation failure

2023-07-19 Thread yuri at tsoft dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110746 --- Comment #7 from Yuri --- gcc-13 has the same problem.

[Bug c++/114652] New: g++ fails to compile the ceres-solver-2.2.0 project: error: use of built-in trait '__remove_cvref(_Tp)' in function signature; use library traits instead

2024-04-08 Thread yuri at tsoft dot com via Gcc-bugs
ts instead Product: gcc Version: 13.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: yuri at tsoft dot com Target Milestone: --- Command and error:

[Bug c++/114878] New: GCC fails with an error on armv7: use of built-in trait '__remove_cvref(_InIter1)' in function signature; use library traits instead

2024-04-28 Thread yuri at tsoft dot com via Gcc-bugs
oduct: gcc Version: 13.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: yuri at tsoft dot com Target Milestone: --- 2 projects where the problem occur

<    1   2