[Bug c++/24561] no static definition

2005-10-27 Thread mark at codesourcery dot com
--- Comment #7 from mark at codesourcery dot com 2005-10-28 02:16 --- Subject: Re: no static definition pinskia at gcc dot gnu dot org wrote: > Not really as unit at a time is considered an optimization and the C++ > front-end just turns it on always. I don't think that

[Bug other/15082] [3.4/4.0/4.1 regression] Minor compilation problem for cross to Solaris 8

2005-10-30 Thread mark at codesourcery dot com
--- Comment #15 from mark at codesourcery dot com 2005-10-30 22:33 --- Subject: Re: [3.4/4.0/4.1 regression] Minor compilation problem for cross to Solaris 8 What's this "4.1blocker-" stuff about? This certainly isn't a 4.1 blocker, and that information is alr

[Bug other/15082] [3.4/4.0/4.1 regression] Minor compilation problem for cross to Solaris 8

2005-10-30 Thread mark at codesourcery dot com
--- Comment #17 from mark at codesourcery dot com 2005-10-30 22:38 --- Subject: Re: [3.4/4.0/4.1 regression] Minor compilation problem for cross to Solaris 8 pinskia at gcc dot gnu dot org wrote: > --- Comment #16 from pinskia at gcc dot gnu dot org 2005-10-30 22

[Bug middle-end/22275] [3.4/4.0/4.1 Regression] bitfield layout change (regression?)

2005-10-30 Thread mark at codesourcery dot com
--- Comment #7 from mark at codesourcery dot com 2005-10-31 07:44 --- Subject: Re: [3.4/4.0/4.1 Regression] bitfield layout change (regression?) steven at gcc dot gnu dot org wrote: > --- Comment #6 from steven at gcc dot gnu dot org 2005-10-31 07:21 > --- > This

[Bug c++/42748] warnings about 'mangling of 'va_list' has changed in GCC 4.4' not suppressed in sytem headers

2010-02-18 Thread mark at codesourcery dot com
--- Comment #21 from mark at codesourcery dot com 2010-02-18 19:47 --- Subject: Re: warnings about 'mangling of 'va_list' has changed in GCC 4.4' not suppressed in sytem headers manu at gcc dot gnu dot org wrote: > In any case, using diagnostic_report_warni

[Bug c++/43680] [DR 1022] G++ is too aggressive in optimizing away bounds checking with enums

2010-04-20 Thread mark at codesourcery dot com
--- Comment #15 from mark at codesourcery dot com 2010-04-20 22:18 --- Subject: Re: [DR 1022] G++ is too aggressive in optimizing away bounds checking with enums jason at gcc dot gnu dot org wrote: > Certainly optimizing away bounds checking is good when it is provably > red

[Bug libstdc++/22111] [4.0 Regression] libstdc++ abi_check

2005-06-22 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-06-22 19:46 --- Subject: Re: [4.0 Regression] libstdc++ abi_check bkoz at gcc dot gnu dot org wrote: > --- Additional Comments From bkoz at gcc dot gnu dot org 2005-06-22 > 18:17 --- > > I'd lik

[Bug c++/21799] [4.0/4.1 regression] Spurious ambiguity with pointers to members

2005-06-23 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-06-23 15:04 --- Subject: Re: [4.0/4.1 regression] Spurious ambiguity with pointers to members bangerth at dealii dot org wrote: > --- Additional Comments From bangerth at dealii dot org 2005-06-23 14

[Bug c++/21799] [4.0/4.1 regression] Spurious ambiguity with pointers to members

2005-06-23 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-06-23 15:20 --- Subject: Re: [4.0/4.1 regression] Spurious ambiguity with pointers to members bangerth at ices dot utexas dot edu wrote: > --- Additional Comments From bangerth at ices dot utexas dot edu > 2

[Bug c++/21799] [4.0/4.1 regression] Spurious ambiguity with pointers to members

2005-06-25 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-06-26 00:45 --- Subject: Re: [4.0/4.1 regression] Spurious ambiguity with pointers to members bangerth at ices dot utexas dot edu wrote: > --- Additional Comments From bangerth at ices dot utexas dot edu > 2

[Bug debug/21828] [4.0/4.1 Regression] debug info omitted for uninitialized variables

2005-07-07 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-07-08 01:56 --- Subject: Re: [4.0/4.1 Regression] debug info omitted for uninitialized variables wilson at specifix dot com wrote: > I think you are just compounding the mistake created by Mark Mitchell's > p

[Bug bootstrap/20155] [4.0 Regression] libgcj build fails with "execvp: /bin/sh: Argument list too long"

2005-07-14 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-07-15 00:30 --- Subject: Re: [4.0 Regression] libgcj build fails with "execvp: /bin/sh: Argument list too long" bonzini at gcc dot gnu dot org wrote: > --- Additional Comments From bonzini at gcc dot gnu

[Bug debug/21828] [4.0/4.1 Regression] debug info omitted for uninitialized variables

2005-07-20 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-07-20 14:40 --- Subject: Re: [4.0/4.1 Regression] debug info omitted for uninitialized variables jakub at redhat dot com wrote: > --- Additional Comments From jakub at redhat dot com 2005-07-20 11:41 > -

[Bug debug/21828] [4.0/4.1 Regression] debug info omitted for uninitialized variables

2005-07-21 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-07-22 06:25 --- Subject: Re: [4.0/4.1 Regression] debug info omitted for uninitialized variables mmitchel at gcc dot gnu dot org wrote: > I will try a test run with my patch reverted; if that passes, and still fi

[Bug debug/21828] [4.0/4.1 Regression] debug info omitted for uninitialized variables

2005-07-21 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-07-22 06:52 --- Subject: Re: [4.0/4.1 Regression] debug info omitted for uninitialized variables mark at codesourcery dot com wrote: > Unfortunately, it failed -- gcc.dg/pch/global-1.c fails at -O3. > > I hav

[Bug debug/21828] [4.0 Regression] debug info omitted for uninitialized variables

2005-07-22 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-07-22 20:49 --- Subject: Re: [4.0 Regression] debug info omitted for uninitialized variables hjl at lucon dot org wrote: > --- Additional Comments From hjl at lucon dot org 2005-07-22 20:44 > --- > M

[Bug c++/18556] [4.0 Regression] C++ debug is broken

2005-07-22 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-07-22 20:51 --- Subject: Re: [4.0 Regression] C++ debug is broken hjl at lucon dot org wrote: > --- Additional Comments From hjl at lucon dot org 2005-07-22 20:45 > --- > The bug came back with the patc

[Bug debug/21828] [4.0 Regression] debug info omitted for uninitialized variables

2005-07-22 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-07-22 21:02 --- Subject: Re: [4.0 Regression] debug info omitted for uninitialized variables hjl at lucon dot org wrote: > --- Additional Comments From hjl at lucon dot org 2005-07-22 20:53 > --- > I a

[Bug debug/21828] [4.0 Regression] debug info omitted for uninitialized variables

2005-07-22 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-07-22 23:43 --- Subject: Re: [4.0 Regression] debug info omitted for uninitialized variables Devang Patel wrote: > > $ gdb --batch -x gdbcmds t > Reading symbols for shared libraries ... done > Breakpoint

[Bug debug/23190] [4.0/4.1 Regression] debug info omitted for uninitialized variables (stabs)

2005-08-01 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-08-02 03:25 --- Subject: Re: [4.0/4.1 Regression] debug info omitted for uninitialized variables (stabs) pinskia at gcc dot gnu dot org wrote: > --- Additional Comments From pinskia at gcc dot gnu dot org 2005-08

[Bug debug/23190] [4.0/4.1 Regression] debug info omitted for uninitialized variables (stabs)

2005-08-02 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-08-02 17:16 --- Subject: Re: [4.0/4.1 Regression] debug info omitted for uninitialized variables (stabs) dpatel at apple dot com wrote: > --- Additional Comments From dpatel at apple dot com 2005-08-02 17

[Bug c++/20589] error: '' is/uses anonymous type'

2005-08-04 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-08-05 03:49 --- Subject: Re: error: '' is/uses anonymous type' sethml at google dot com wrote: > --- Additional Comments From sethml at google dot com 2005-08-05 03:43 > --- > The C++ wor

[Bug c++/20646] [4.0/4.1 Regression] ICE on illegal code: "extern static" struct member

2005-08-09 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-08-09 23:53 --- Subject: Re: [4.0/4.1 Regression] ICE on illegal code: "extern static" struct member reichelt at gcc dot gnu dot org wrote: > --- Additional Comments From reichelt at gcc dot gnu dot or

[Bug rtl-optimization/23561] nonoverlapping_memrefs_p returns true even for overlapping memory references

2005-08-25 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-08-25 17:22 --- Subject: Re: nonoverlapping_memrefs_p returns true even for overlapping memory references rth at gcc dot gnu dot org wrote: > And in the case in question, it's quite obviously an off-by-one bu

[Bug tree-optimization/39251] FAIL: g++.dg/tree-ssa/new1.C scan-tree-dump-not forwprop1 "= .* \+ -"

2010-01-15 Thread mark at codesourcery dot com
--- Comment #10 from mark at codesourcery dot com 2010-01-15 15:05 --- Subject: Re: FAIL: g++.dg/tree-ssa/new1.C scan-tree-dump-not forwprop1 "= .* \+ -" ramana at gcc dot gnu dot org wrote: > So yes it does look ARM specific . Also peeking at results on gcc-testresu

[Bug c++/42748] warnings about 'mangling of 'va_list' has changed in GCC 4.4' not suppressed in sytem headers

2010-01-27 Thread mark at codesourcery dot com
--- Comment #9 from mark at codesourcery dot com 2010-01-27 20:04 --- Subject: Re: warnings about 'mangling of 'va_list' has changed in GCC 4.4' not suppressed in sytem headers paolo dot carlini at oracle dot com wrote: > If you say 'consider' and

[Bug c++/42748] warnings about 'mangling of 'va_list' has changed in GCC 4.4' not suppressed in sytem headers

2010-01-29 Thread mark at codesourcery dot com
--- Comment #15 from mark at codesourcery dot com 2010-01-29 15:12 --- Subject: Re: warnings about 'mangling of 'va_list' has changed in GCC 4.4' not suppressed in sytem headers manu at gcc dot gnu dot org wrote: > Why is this a note and not simply a warn

[Bug lto/45375] [meta-bug] Issues with building Mozilla with LTO

2011-04-04 Thread mark at codesourcery dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45375 --- Comment #69 from Mark Mitchell 2011-04-05 00:16:02 UTC --- On 4/4/2011 3:19 AM, froydnj at codesourcery dot com wrote: > Do folks think it would be useful to include a breakdown by individual > TREE_CODE, similar to what's done for RTXes? S

[Bug target/46770] Replace .ctors/.dtors with .init_array/.fini_array on targets supporting them

2010-12-11 Thread mark at codesourcery dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46770 --- Comment #16 from Mark Mitchell 2010-12-11 18:50:11 UTC --- On 12/11/2010 10:47 AM, hjl.tools at gmail dot com wrote: > Linker supports sorting .ctors.N and .init_array.. > Within .ctors.N and .init_array., the order is define

[Bug target/46770] Replace .ctors/.dtors with .init_array/.fini_array on targets supporting them

2010-12-11 Thread mark at codesourcery dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46770 --- Comment #18 from Mark Mitchell 2010-12-11 19:33:17 UTC --- On 12/11/2010 11:03 AM, hjl.tools at gmail dot com wrote: > I am not sure about GOLD. But it usually follows GNU linker. > For GNU linker, the constructor priority is honored within

[Bug target/46770] Replace .ctors/.dtors with .init_array/.fini_array on targets supporting them

2010-12-11 Thread mark at codesourcery dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46770 --- Comment #24 from Mark Mitchell 2010-12-11 19:56:43 UTC --- On 12/11/2010 11:53 AM, hjl.tools at gmail dot com wrote: >> You have to be more specific about what you meant by "interleaving". Constructor priorities are a GNU C extension: __

[Bug target/46770] Replace .ctors/.dtors with .init_array/.fini_array on targets supporting them

2010-12-11 Thread mark at codesourcery dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46770 --- Comment #27 from Mark Mitchell 2010-12-11 20:19:23 UTC --- On 12/11/2010 12:17 PM, hjl.tools at gmail dot com wrote: > I don't think GCC really supports interleaving constructor priority > at binary level. Unless GCC can guarantees one can i

[Bug target/46770] Replace .ctors/.dtors with .init_array/.fini_array on targets supporting them

2010-12-11 Thread mark at codesourcery dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46770 --- Comment #29 from Mark Mitchell 2010-12-11 21:06:41 UTC --- On 12/11/2010 1:01 PM, hubicka at ucw dot cz wrote: > So I take that, the ctor order is to support priotities, since the > .ctor.priority sections get merged into single and ordered

[Bug target/46770] Replace .ctors/.dtors with .init_array/.fini_array on targets supporting them

2010-12-11 Thread mark at codesourcery dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46770 --- Comment #32 from Mark Mitchell 2010-12-11 23:19:05 UTC --- On 12/11/2010 2:56 PM, hjl.tools at gmail dot com wrote: > It works at source code level. I don't believe we ever support > "interleaving constructor priorities" between object files

[Bug target/46770] Replace .ctors/.dtors with .init_array/.fini_array on targets supporting them

2010-12-11 Thread mark at codesourcery dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46770 --- Comment #34 from Mark Mitchell 2010-12-11 23:30:19 UTC --- On 12/11/2010 3:28 PM, hjl.tools at gmail dot com wrote: > 1. How do you find out what priority "foo" constructor has? If you're looking at source code, read the source. If you're

[Bug target/46770] Replace .ctors/.dtors with .init_array/.fini_array on targets supporting them

2010-12-11 Thread mark at codesourcery dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46770 --- Comment #36 from Mark Mitchell 2010-12-11 23:54:44 UTC --- On 12/11/2010 3:48 PM, hjl.tools at gmail dot com wrote: > 1. __attribute__((init_priority(1005))) doesn't map to > .ctors.1005 section. It probably maps to .ctors.(65535-1005). T

[Bug target/46770] Replace .ctors/.dtors with .init_array/.fini_array on targets supporting them

2010-12-11 Thread mark at codesourcery dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46770 --- Comment #38 from Mark Mitchell 2010-12-12 00:03:22 UTC --- On 12/11/2010 4:00 PM, hjl.tools at gmail dot com wrote: > Really? Here is a testcase. Do you think goo's constructor > will be called before another constructor in another file > w

[Bug target/46770] Replace .ctors/.dtors with .init_array/.fini_array on targets supporting them

2010-12-11 Thread mark at codesourcery dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46770 --- Comment #40 from Mark Mitchell 2010-12-12 00:11:56 UTC --- On 12/11/2010 4:08 PM, hjl.tools at gmail dot com wrote: > We only support constructor priority in single source file: H.J., this is false. Please try writing three constructors, w

[Bug target/46770] Replace .ctors/.dtors with .init_array/.fini_array on targets supporting them

2010-12-11 Thread mark at codesourcery dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46770 --- Comment #43 from Mark Mitchell 2010-12-12 00:24:30 UTC --- On 12/11/2010 4:20 PM, hjl.tools at gmail dot com wrote: > That means we only guarantee constructor priorities in one TU and > my testcase confirms it. HJ, this isn't true. The exp

[Bug target/46770] Replace .ctors/.dtors with .init_array/.fini_array on targets supporting them

2010-12-12 Thread mark at codesourcery dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46770 --- Comment #46 from Mark Mitchell 2010-12-12 18:40:35 UTC --- On 12/11/2010 4:32 PM, hjl.tools at gmail dot com wrote: > Mark, I may have misunderstood you. Correct me if I am wrong. > Currently, it may be possible to interleave constructors >

[Bug target/46770] Replace .ctors/.dtors with .init_array/.fini_array on targets supporting them

2010-12-14 Thread mark at codesourcery dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46770 --- Comment #62 from Mark Mitchell 2010-12-14 15:17:25 UTC --- > Having everyone with knowledge of static construction alerted, can't we use > the > GNU constructor priorities to solve PR44952? The two constraints are: (a) priorities aren't su

[Bug target/33579] INIT_PRIORITY is broken

2007-10-28 Thread mark at codesourcery dot com
--- Comment #6 from mark at codesourcery dot com 2007-10-28 22:46 --- Subject: Re: INIT_PRIORITY is broken danglin at gcc dot gnu dot org wrote: > With respect to initpr1.c, it can be seen that only one "GLOBAL" constructor, > _GLOBAL__I_0_c1, and one &qu

[Bug target/33579] INIT_PRIORITY is broken

2007-10-29 Thread mark at codesourcery dot com
--- Comment #8 from mark at codesourcery dot com 2007-10-30 02:50 --- Subject: Re: INIT_PRIORITY is broken dave at hiauly1 dot hia dot nrc dot ca wrote: >> I don't think this will be too hard to implement. In >> cgraph_build_cdtor_fns, we need to partition/sort th

[Bug target/33579] INIT_PRIORITY is broken

2007-11-01 Thread mark at codesourcery dot com
--- Comment #12 from mark at codesourcery dot com 2007-11-01 16:50 --- Subject: Re: INIT_PRIORITY is broken danglin at gcc dot gnu dot org wrote: > --- Comment #11 from danglin at gcc dot gnu dot org 2007-11-01 03:05 > --- > Mark, > > This is major pro

[Bug middle-end/32044] [4.3 regression] udivdi3 counterproductive, unwarranted use

2007-11-27 Thread mark at codesourcery dot com
--- Comment #30 from mark at codesourcery dot com 2007-11-27 18:58 --- Subject: Re: [4.3 regression] udivdi3 counterproductive, unwarranted use rguenth at gcc dot gnu dot org wrote: > --- Comment #29 from rguenth at gcc dot gnu dot org 2007-11-27 09:43 > --- > Thi

[Bug middle-end/32044] [4.3 regression] udivdi3 counterproductive, unwarranted use

2007-11-27 Thread mark at codesourcery dot com
--- Comment #35 from mark at codesourcery dot com 2007-11-27 19:45 --- Subject: Re: [4.3 regression] udivdi3 counterproductive, unwarranted use bunk at stusta dot de wrote: > Even if this specific issue in the kernel would turn out as a misoptimization, > the general problem

[Bug libstdc++/33831] [4.3 Regression] Revision 129442 breaks libstc++ API

2007-12-16 Thread mark at codesourcery dot com
--- Comment #15 from mark at codesourcery dot com 2007-12-17 04:34 --- Subject: Re: [4.3 Regression] Revision 129442 breaks libstc++ API rguenther at suse dot de wrote: > Now that we have ext/hash_map and ext/hash_set back (yes, SPEC2000 > eon still is broken, as it uses the r

[Bug c++/31780] [4.2/4.3 regression] ICE with incompatible types for ?: with "complex type" conversion

2007-12-26 Thread mark at codesourcery dot com
--- Comment #18 from mark at codesourcery dot com 2007-12-26 21:19 --- Subject: Re: [4.2/4.3 regression] ICE with incompatible types for ?: with "complex type" conversion gdr at gcc dot gnu dot org wrote: > I'm very nervous about adding more constructors. > I

[Bug middle-end/32044] [4.3 regression] udivdi3 counterproductive, unwarranted use

2008-01-03 Thread mark at codesourcery dot com
--- Comment #39 from mark at codesourcery dot com 2008-01-04 04:43 --- Subject: Re: [4.3 regression] udivdi3 counterproductive, unwarranted use fche at redhat dot com wrote: >> Downgrading to P4. We seem to have consensus that this is [not] a GCC >> wrong-code >&

[Bug c++/31780] [4.2/4.3 regression] ICE with incompatible types for ?: with "complex type" conversion

2008-01-04 Thread mark at codesourcery dot com
--- Comment #22 from mark at codesourcery dot com 2008-01-05 07:55 --- Subject: Re: [4.2/4.3 regression] ICE with incompatible types for ?: with "complex type" conversion gdr at cs dot tamu dot edu wrote: > | > I'd rather distinguish the constructor taking

[Bug c++/31780] [4.2/4.3 regression] ICE with incompatible types for ?: with "complex type" conversion

2008-01-06 Thread mark at codesourcery dot com
--- Comment #24 from mark at codesourcery dot com 2008-01-06 21:06 --- Subject: Re: [4.2/4.3 regression] ICE with incompatible types for ?: with "complex type" conversion gdr at cs dot tamu dot edu wrote: > | I'm not sure what you mean by that. It's a pub

[Bug c++/31780] [4.2/4.3 regression] ICE with incompatible types for ?: with "complex type" conversion

2008-01-06 Thread mark at codesourcery dot com
--- Comment #26 from mark at codesourcery dot com 2008-01-07 01:16 --- Subject: Re: [4.2/4.3 regression] ICE with incompatible types for ?: with "complex type" conversion gdr at cs dot tamu dot edu wrote: > I would not bet money that nobody is not using it. However, th

[Bug c++/31780] [4.2/4.3 regression] ICE with incompatible types for ?: with "complex type" conversion

2008-01-06 Thread mark at codesourcery dot com
--- Comment #30 from mark at codesourcery dot com 2008-01-07 07:44 --- Subject: Re: [4.2/4.3 regression] ICE with incompatible types for ?: with "complex type" conversion gdr at cs dot tamu dot edu wrote: > | Is it conceivable that ISO C++ will ever add a > | comp

[Bug c++/31780] [4.2/4.3 regression] ICE with incompatible types for ?: with "complex type" conversion

2008-01-06 Thread mark at codesourcery dot com
--- Comment #31 from mark at codesourcery dot com 2008-01-07 07:48 --- Subject: Re: [4.2/4.3 regression] ICE with incompatible types for ?: with "complex type" conversion gdr at cs dot tamu dot edu wrote: > But, as that hypothetical user, I would not have any ground

[Bug c++/31780] [4.2/4.3 regression] ICE with incompatible types for ?: with "complex type" conversion

2008-01-07 Thread mark at codesourcery dot com
--- Comment #34 from mark at codesourcery dot com 2008-01-07 16:17 --- Subject: Re: [4.2/4.3 regression] ICE with incompatible types for ?: with "complex type" conversion gdr at cs dot tamu dot edu wrote: > | What's the likely change? > > Ban implicit narro

[Bug c++/31780] [4.2/4.3 regression] ICE with incompatible types for ?: with "complex type" conversion

2008-01-07 Thread mark at codesourcery dot com
--- Comment #36 from mark at codesourcery dot com 2008-01-08 03:39 --- Subject: Re: [4.2/4.3 regression] ICE with incompatible types for ?: with "complex type" conversion gdr at cs dot tamu dot edu wrote: > | (Both have > | values unrepresentable in the other, of

[Bug libstdc++/33831] [4.3 Regression] Revision 129442 breaks libstc++ API

2008-01-16 Thread mark at codesourcery dot com
--- Comment #25 from mark at codesourcery dot com 2008-01-16 22:27 --- Subject: Re: [4.3 Regression] Revision 129442 breaks libstc++ API bkoz at gcc dot gnu dot org wrote: > I believe there is a bit of a bias here, in that it's OK to make FE changes, > but even well-doc

[Bug testsuite/36443] [4.3/4.4 Regression]: HOSTCC doesn't work with unstalled gcc

2008-06-08 Thread mark at codesourcery dot com
--- Comment #9 from mark at codesourcery dot com 2008-06-08 20:23 --- Subject: Re: [4.3/4.4 Regression]: HOSTCC doesn't work with unstalled gcc hjl dot tools at gmail dot com wrote: > How does gcc search the right paths when GCC_EXEC_PREFIX points > to non-existent direct

[Bug testsuite/36443] [4.3/4.4 Regression]: HOSTCC doesn't work with unstalled gcc

2008-06-08 Thread mark at codesourcery dot com
--- Comment #11 from mark at codesourcery dot com 2008-06-08 21:12 --- Subject: Re: [4.3/4.4 Regression]: HOSTCC doesn't work with unstalled gcc hjl dot tools at gmail dot com wrote: >> I suspect that if you remove the setting in site.exp you will break the >> f

[Bug testsuite/36443] [4.3/4.4 Regression]: HOSTCC doesn't work with unstalled gcc

2008-06-08 Thread mark at codesourcery dot com
--- Comment #13 from mark at codesourcery dot com 2008-06-09 00:05 --- Subject: Re: [4.3/4.4 Regression]: HOSTCC doesn't work with unstalled gcc hjl dot tools at gmail dot com wrote: >>>> 1. User puts libraries/headers in $pefix/{lib,include} >>>

[Bug testsuite/36443] [4.3/4.4 Regression]: HOSTCC doesn't work with installed gcc

2008-06-09 Thread mark at codesourcery dot com
--- Comment #17 from mark at codesourcery dot com 2008-06-09 21:16 --- Subject: Re: [4.3/4.4 Regression]: HOSTCC doesn't work with unstalled gcc hjl dot tools at gmail dot com wrote: > --- Comment #16 from hjl dot tools at gmail dot com 2008-06-09 14:16 > --- >

[Bug testsuite/36443] [4.3/4.4 Regression]: HOSTCC doesn't work with installed gcc

2008-06-09 Thread mark at codesourcery dot com
--- Comment #19 from mark at codesourcery dot com 2008-06-10 00:38 --- Subject: Re: [4.3/4.4 Regression]: HOSTCC doesn't work with installed gcc hjl dot tools at gmail dot com wrote: > They sound to me the ideal usage for --sysroot. They aren't from > gcc and they d

[Bug testsuite/36443] [4.3/4.4 Regression]: HOSTCC doesn't work with installed gcc

2008-06-09 Thread mark at codesourcery dot com
--- Comment #21 from mark at codesourcery dot com 2008-06-10 05:02 --- Subject: Re: [4.3/4.4 Regression]: HOSTCC doesn't work with installed gcc hjl dot tools at gmail dot com wrote: >>> --syroot supports libraries and headers. Does it support >>> assemble

[Bug c++/36760] Simple std::bind use causes warnings with -Wextra

2008-07-08 Thread mark at codesourcery dot com
--- Comment #6 from mark at codesourcery dot com 2008-07-08 16:32 --- Subject: Re: Simple std::bind use causes warnings with -Wextra paolo dot carlini at oracle dot com wrote: > Thanks Tom. In fact, yesterday I was writing without remembering my past > analyses of this type of

[Bug c++/36760] Simple std::bind use causes warnings with -Wextra

2008-07-09 Thread mark at codesourcery dot com
--- Comment #13 from mark at codesourcery dot com 2008-07-09 19:08 --- Subject: Re: Simple std::bind use causes warnings with -Wextra bangerth at dealii dot org wrote: > --- Comment #10 from bangerth at dealii dot org 2008-07-09 17:04 --- > (In reply to comment #8) &g

[Bug c++/36633] [4.4 regression] warning "array subscript is below array bounds" on delete [] with -O2, -Wall

2008-07-09 Thread mark at codesourcery dot com
--- Comment #9 from mark at codesourcery dot com 2008-07-10 03:42 --- Subject: Re: [4.4 regression] warning "array subscript is below array bounds" on delete [] with -O2, -Wall paolo dot carlini at oracle dot com wrote: > Mark, could you possibly comment on this PR? W

[Bug c++/36633] [4.4 regression] warning "array subscript is below array bounds" on delete [] with -O2, -Wall

2008-07-10 Thread mark at codesourcery dot com
--- Comment #14 from mark at codesourcery dot com 2008-07-10 14:58 --- Subject: Re: [4.4 regression] warning "array subscript is below array bounds" on delete [] with -O2, -Wall rguenther at suse dot de wrote: > Can the FE mark this array-access with TREE_NO_WARNING?

[Bug c++/36797] ICE on SFINAE and __is_empty

2008-07-14 Thread mark at codesourcery dot com
--- Comment #7 from mark at codesourcery dot com 2008-07-14 15:28 --- Subject: Re: ICE on SFINAE and __is_empty sebor at roguewave dot com wrote: > My preference would be for gcc to avoid imposing restrictions on the use > of these helpers to facilitate portability to other com

[Bug c++/36797] ICE on SFINAE and __is_empty

2008-07-14 Thread mark at codesourcery dot com
--- Comment #9 from mark at codesourcery dot com 2008-07-14 16:53 --- Subject: Re: ICE on SFINAE and __is_empty sebor at roguewave dot com wrote: > int foo >(B, __is_empty (A<0>)>::X*): > _Z3fooI1AILi0EEEiPN1BIT_Xv19builtin16TOS3_EE1XE >

[Bug c++/24996] [4.0/4.1/4.2 Regression] ICE on throw code

2006-02-01 Thread mark at codesourcery dot com
--- Comment #19 from mark at codesourcery dot com 2006-02-01 08:21 --- Subject: Re: [4.0/4.1/4.2 Regression] ICE on throw code rakdver at atrey dot karlin dot mff dot cuni dot cz wrote: >>Zdenek, have you submitted the patch yet for mainline? > > no, I was waiting for

[Bug target/21623] [4.0/4.1 regression] ICE in reload_cse_simplify_operands, at postreload.c:391

2006-02-13 Thread mark at codesourcery dot com
--- Comment #8 from mark at codesourcery dot com 2006-02-14 01:21 --- Subject: Re: [4.0/4.1 regression] ICE in reload_cse_simplify_operands, at postreload.c:391 Joern RENNECKE wrote: > No, it is just a matter of what is desired for the branch. Mark, would > you like &

[Bug c++/26266] [4.0/4.1/4.2 regression] Trouble with static const data members in template classes

2006-02-14 Thread mark at codesourcery dot com
--- Comment #6 from mark at codesourcery dot com 2006-02-14 19:26 --- Subject: Re: [4.0/4.1/4.2 regression] Trouble with static const data members in template classes reichelt at gcc dot gnu dot org wrote: > --- Comment #5 from reichelt at gcc dot gnu dot org 2006-02-14 17

[Bug middle-end/25335] [4.1/4.2 Regression] reload leaves insns from earlier passes around: fatal for postinc

2006-02-14 Thread mark at codesourcery dot com
--- Comment #17 from mark at codesourcery dot com 2006-02-15 01:56 --- Subject: Re: [4.1/4.2 Regression] reload leaves insns from earlier passes around: fatal for postinc Joern RENNECKE wrote: > I have started regression tests for i686-pc-linux-gnu native, X arm-elf, > X cris-

[Bug inline-asm/23200] [4.0/4.1/4.2 regression] rejects "i"(&var + 1)

2006-02-23 Thread mark at codesourcery dot com
--- Comment #20 from mark at codesourcery dot com 2006-02-24 02:17 --- Subject: Re: [4.0/4.1/4.2 regression] rejects "i"(&var + 1) mrs at apple dot com wrote: > --- Comment #19 from mrs at apple dot com 2006-02-24 02:14 --- > This was not 4.1.0 before, it

[Bug target/26459] [4.1/4.2 Regression] gcc fails to build on powerpc e500-double targets

2006-02-24 Thread mark at codesourcery dot com
--- Comment #6 from mark at codesourcery dot com 2006-02-24 19:14 --- Subject: Re: [4.1/4.2 Regression] gcc fails to build on powerpc e500-double targets edmar at freescale dot com wrote: > I started a build. This is a very slow target, it will take several hours... If you'

[Bug target/26459] [4.1/4.2 Regression] gcc fails to build on powerpc e500-double targets

2006-02-24 Thread mark at codesourcery dot com
--- Comment #8 from mark at codesourcery dot com 2006-02-24 21:07 --- Subject: Re: [4.1/4.2 Regression] gcc fails to build on powerpc e500-double targets edmar at freescale dot com wrote: > --- Comment #7 from edmar at freescale dot com 2006-02-24 20:45 --- > Crea

[Bug c++/25632] [4.0 Regression] ICE with const int copied into two different functions

2006-02-27 Thread mark at codesourcery dot com
--- Comment #19 from mark at codesourcery dot com 2006-02-28 00:25 --- Subject: Re: [4.0 Regression] ICE with const int copied into two different functions rakdver at atrey dot karlin dot mff dot cuni dot cz wrote: > --- Comment #18 from rakdver at atrey dot karlin dot mff

[Bug c++/21087] [4.0/4.1 Regression] ICE in do_nonmember_using_decl

2005-04-21 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-04-22 00:58 --- Subject: Re: [PR c++/21087] don't keep builtin anticipated decl, override it with actual declaration Alexandre Oliva wrote: > When push_overloaded_decl() was passed a new declaration that mat

[Bug c++/21087] [4.0 Regression] ICE in do_nonmember_using_decl

2005-04-24 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-04-24 17:05 --- Subject: Re: [PR c++/21087] don't keep builtin anticipated decl, override it with actual declaration Alexandre Oliva wrote: > > Ok for 4.0 branch as well? The same patch applies cleanly there,

[Bug c++/21339] [3.4 regression] ICE with pointer to member in template

2005-05-02 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-05-02 14:56 --- Subject: Re: New: [3.4 regression] ICE with pointer to member in template reichelt at gcc dot gnu dot org wrote: > The testcase in PR 15875 started ICE'ing on the 3.4 branch again: > Mark, t

[Bug rtl-optimization/15248] [4.0 Regression] Reload may generate stores to read-only memory

2005-05-03 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-05-03 19:35 --- Subject: Re: [4.0 Regression] Reload may generate stores to read-only memory Jeffrey A Law wrote: > On Sat, 2005-04-30 at 22:10 +, ebotcazou at gcc dot gnu dot org >

[Bug rtl-optimization/18081] [3.4 regression] Infinite memory allocation on -O3

2005-05-04 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-05-04 16:33 --- Subject: Re: [3.4 regression] Infinite memory allocation on -O3 giovannibajo at libero dot it wrote: > --- Additional Comments From giovannibajo at libero dot it 2005-05-04 > 12:12 --- &

[Bug rtl-optimization/15248] [4.0 Regression] Reload may generate stores to read-only memory

2005-05-08 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-05-09 00:20 --- Subject: Re: [4.0 Regression] Reload may generate stores to read-only memory ebotcazou at gcc dot gnu dot org wrote: > --- Additional Comments From ebotcazou at gcc dot gnu dot org 2005-05-07 >

[Bug rtl-optimization/18081] [3.4 regression] Infinite memory allocation on -O3

2005-05-10 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-05-10 15:20 --- Subject: Re: [3.4 regression] Infinite memory allocation on -O3 schwab at suse dot de wrote: > --- Additional Comments From schwab at suse dot de 2005-05-10 13:23 > --- > This is

[Bug libstdc++/21523] [3.4/4.0 Regression] 3.4.4 RC1 fails libstdc++ install on powerpc64-linux

2005-05-11 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-05-11 23:06 --- Subject: Re: New: 3.4.4 RC1 fails libstdc++ install on powerpc64-linux janis at gcc dot gnu dot org wrote: > GCC 3.4.4 RC1 fails "make install" for powerpc64-linux. Recent builds > from

[Bug libstdc++/21526] libstdc++-v3 testsuite hangs on cygwin

2005-05-12 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-05-12 15:15 --- Subject: Re: libstdc++-v3 testsuite hangs on cygwin pcarlini at suse dot de wrote: > --- Additional Comments From pcarlini at suse dot de 2005-05-12 10:02 > --- > In other terms, we sh

[Bug libstdc++/21526] libstdc++-v3 testsuite hangs on cygwin

2005-05-12 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-05-12 15:32 --- Subject: Re: libstdc++-v3 testsuite hangs on cygwin pcarlini at suse dot de wrote: > --- Additional Comments From pcarlini at suse dot de 2005-05-12 15:23 > --- > Thanks a lot Mark. At t

[Bug libstdc++/21523] [3.4/4.0 Regression] 3.4.4 RC1 fails libstdc++ install on powerpc64-linux

2005-05-12 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-05-12 18:06 --- Subject: Re: New: 3.4.4 RC1 fails libstdc++ install on powerpc64-linux Janis -- Would you please try the attached patch for 3.4? I have a similar patch for 4.0 which I will attach soon. If this doesn&#

[Bug libstdc++/21526] libstdc++-v3 testsuite hangs on cygwin

2005-05-12 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-05-13 00:37 --- Subject: Re: libstdc++-v3 testsuite hangs on cygwin david dot billinghurst at comalco dot riotinto dot com dot au wrote: > --- Additional Comments From david dot billinghurst at comalco dot > ri

[Bug libstdc++/21523] [4.0 Regression] 3.4.4 RC1 fails libstdc++ install on powerpc64-linux

2005-05-12 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-05-13 01:01 --- Subject: Re: [4.0 Regression] 3.4.4 RC1 fails libstdc++ install on powerpc64-linux mmitchel at gcc dot gnu dot org wrote: > --- Additional Comments From mmitchel at gcc dot gnu dot org 2005-05

[Bug middle-end/21538] [4.0/4.1 Regression] g++.dg/opt/temp1.C execution test fails

2005-05-12 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-05-13 06:18 --- Subject: Re: [4.0/4.1 Regression] g++.dg/opt/temp1.C execution test fails pinskia at gcc dot gnu dot org wrote: > --- Additional Comments From pinskia at gcc dot gnu dot org 2005-05-12 >

[Bug middle-end/21538] g++.dg/opt/temp1.C should be optimized elsewhere

2005-05-15 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-05-16 00:17 --- Subject: Re: g++.dg/opt/temp1.C should be optimized elsewhere rguenth at gcc dot gnu dot org wrote: > --- Additional Comments From rguenth at gcc dot gnu dot org 2005-05-15 > 19:30 ---

[Bug libstdc++/19664] libstdc++ headers should have pop/push of the visibility around the declarations

2005-05-17 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-05-17 21:40 --- Subject: Re: libstdc++ headers should have pop/push of the visibility around the declarations pcarlini at suse dot de wrote: > --- Additional Comments From pcarlini at suse dot de 2005-05-17 19

[Bug libstdc++/19664] libstdc++ headers should have pop/push of the visibility around the declarations

2005-05-17 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-05-17 21:58 --- Subject: Re: libstdc++ headers should have pop/push of the visibility around the declarations hjl at lucon dot org wrote: > --- Additional Comments From hjl at lucon dot org 2005-05-17 21

[Bug libstdc++/19664] libstdc++ headers should have pop/push of the visibility around the declarations

2005-05-19 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-05-19 19:21 --- Subject: Re: libstdc++ headers should have pop/push of the visibility around the declarations bernie at develer dot com wrote: > It's not a regresion, but it causes KDE to miscompile > wit

[Bug libstdc++/19664] libstdc++ headers should have pop/push of the visibility around the declarations

2005-05-20 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-05-20 18:48 --- Subject: Re: libstdc++ headers should have pop/push of the visibility around the declarations lanius at gentoo dot org wrote: > --- Additional Comments From lanius at gentoo dot org 2005-05-20 08

[Bug c++/17413] [3.4 regression] local classes as template argument

2005-05-29 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-05-29 17:18 --- Subject: Re: [3.4 regression] local classes as template argument Geoffrey Keating wrote: > Hi Mark, > > Consider this code: > > struct Attribute { }; > template void fun (const Attrib

[Bug c++/21619] [4.0 regression] __builtin_constant_p(&"Hello"[0])?1:-1 not compile-time constant

2005-06-05 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-06-05 17:35 --- Subject: Re: [4.0 regression] __builtin_constant_p(&"Hello"[0])?1:-1 not compile-time constant pinskia at gcc dot gnu dot org wrote: > --- Additional Comments From pinskia at gcc dot

[Bug c++/21619] [4.0 regression] __builtin_constant_p(&"Hello"[0])?1:-1 not compile-time constant

2005-06-05 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-06-05 17:57 --- Subject: Re: [4.0 regression] __builtin_constant_p(&"Hello"[0])?1:-1 not compile-time constant mark at codesourcery dot com wrote: > --- Additional Comments From mark at codesourcery

[Bug debug/21828] [4.0/4.1 Regression] debug info omitted for global variables

2005-06-05 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-06-06 00:15 --- Subject: Re: [4.0/4.1 Regression] debug info omitted for global variables pinskia at gcc dot gnu dot org wrote: > --- Additional Comments From pinskia at gcc dot gnu dot org 2005-06-05 >

<    1   2   3   4   >