Re: GCC 4.1: Buildable on GHz machines only?
--- Tom Tromey wrote: > I'm not sure what Plan B would be. Maybe separate > libgcj releases > somehow. You coulder consider just having GCJ inside GCC but somehow get it to use GNU Classpath directly, this would also reduce it needing to be re-sync with GNU Classpath (which I beleive libgcj is based on it) and allows you deliver a more up-to-date Java library to people faster. ___ How much free photo storage do you get? Store your holiday snaps for FREE with Yahoo! Photos http://uk.photos.yahoo.com
Re: subscription to gcc mailing list
--- drugdesign wrote: > How can I subscribe to GCC mailing list? Look at http://www.gnu.org/software/gcc/lists.html under section titled "Subscribing/unsubscribing" ___ How much free photo storage do you get? Store your holiday snaps for FREE with Yahoo! Photos http://uk.photos.yahoo.com
Re: What is wrong with Bugzilla? [Was: Re: GCC and Floating-Point]
--- Uros Bizjak wrote: > At this point, I wonder what is wrong with Bugzilla, > that those > programmers don't fill a proper bug report. If there > is a problem with > GCC, that is so annoying to somebody, I think that > at least developers > could be informed about it via their standard > channels of communication. > If there is a specific problem, at least it can be > analysed properly and > perhaps some actions could be taken to fix it. If > the problem is indeed > _that_ big (usually, it is not!), then a workaround > could be suggested - > and this bug, together with a workaround is > documented in bugzilla for > others, until the problem is properly solved > (usually with a testcase). > I guess that these persons don't know that > bugreports are extremmely > important for the development of gcc. The users > themself are actaully a > QA department of open source development;) > > There is no problem that Bugzilla is un-intuitive, > it is far from that. > The users don't fill bugreports because they are > afraid of filling an > invalid report or a duplicate. I can't speak for gcc > bugmasters, but it > looks to me that dupes and invalid reports are not > that big problem. t if people sit 3000 km/miles/whatever apart > ;) > You can search Bugzilla as well, so you do not fill in duplicate bug report. As long as the bug report can be easily reproduced, it will probably not get made invalid. ___ Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com
Re: What is wrong with Bugzilla? [Was: Re: GCC and Floating-Point]
--- Michael Veksler wrote:
> Unfortunately, this is not 100% correct. Recently I
> have filed several
> duplicates, *after* searching Bugzilla.
> 1. There are too many ways to phrase a title, and
> too many
>times I search for wrong words.
>
> 2. The same bug may have several different user
>visible behaviors. You will end up with at least
> one
>duplicate per user visible behavior.
>
>At work, I maintain a bug database for my project
> and I
>sometimes need to fire-up a debugger to find out
> that
>a reported bug is a well known one.
>
>Many times only a trained developer (in the
> project) can assert
>that a PR is indeed a duplicate of another one.
>
> 3. Nontrivial search of GCC Bugzilla are, sometimes,
>extremely slow (over a minute). This inhibits
> multiple
>searches. I usually give up after the first one,
> and don't
>bother with a different type of query (which
> could have
>revealed a similar PR).
Sometimes it is difficult.
Exposing different visibility behaviors of the bug,
being filling in can save another person filing yet
another duplicate as they can maybe find it in their
search.
Having different visibility behaviour of the bug being
put in Bugzilla is good IMHO.
> Mostly true, but not always. Bugs will be normally
> marked
> invalid when the bug is in other parts of the
> toolchnain, or
> in the processor. This happens even when it is
> possible to
> implement a work-around in gcc.
>
> Two examples come in mind:
> 1. Non conformance of x86 to the standard FP due to
>its extra precision. This includes different
> results
>between -O2 and -O0 even with -fsave-temps.
>Several PR about this issue were marked invalid
> in
>the past.
>This is a bug in two places:
> i. x86 FP which implements wrong precision.
> ii. glibc that claims in its headers that it
> sets to set
>default precision to 64 bits, when in
> practice it
>sets it to 80 bits.
> Nevertheless, gcc can implement a work-around.
> The
> PRs may have stayed open with a low priority,
> putting
> the issue on a list of projects that someone may
> want
> to pick up.
> 2. GDB crashes on AIX because a bug in either gcc,
> gdb,
>or the native /bin/as. Every one of these tools
> points
>fingers to the other direction. I tend to believe
> the bug
>is in GDB
>
>
http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gdb&pr=1170
>yet, the work-around in gcc is only 2 lines.
>If GCC and GDB were one project instead of two,
> it is
>possible that the work-around approach would be
> implemented.
>But because GDB is a different project, and the
> fix is nontrivial [1]
>it will probably be never fixed (unless AIX moves
> to dwarf).
>
> Technically speaking, these are not GCC bugs.
> However, from
> user's POV they *are* GCC bugs. This mismatch
> between user
> and developer perceptions is not very healthy and
> may inhibit
> other PRs. Maybe developers should be more open to
> "fixing"
> things that are not purely GCC bugs?
That's a problem with some of these GCC bugmasters (no
names mentioned) for classify them as not gcc bugs. I
have also been hit by similar problem but it got
fixed.
The toolchain packages are not always in sync. Getting
prerequisite for a toolchain is not that simple at
all.
Some of these problems can limit the usability of GCC,
ie toolchain problem preventing GCC to bootstrap or to
cause other errors.
>
> Another thing that intimidates users is the
> complexity of
> C and C++. Things that may look like bugs are not
> really
> bugs:
> 1. Undefined (unspecified?) behavior due to aliasing
> rules.
> 2. Two stage name lookup in templates is confusing.
>Because of that I will not report a bug related
> to templates,
>before mailing a query to [EMAIL PROTECTED]
>It is not only a "fault" of ISO C++, but also of
> gcc [2].
>
>
>
> [1] The fix could be trivial, but I could not find
> it. Despite having no
> time to learn neither GCC nor GDB source I was
> able to
>1. Follow the bug from GDB crash back to GCC.
>2. Find how to trivially "fix" it in GCC.
>3. Yet I was unable to find how to fix GDB.
>This leads me to believe that fixing GDB is more
> difficult.
Yes, bugs in GDB are much difficult.
> [2] GCC could implement a better error message. An
> example
> for a good report is:
> $ cat t.cpp
> int f() {
> for (int i=0 ; i < 10 ; ++i)
> {}
> return i;
> }
> $ g++ t.cpp
> t.cpp: In function 'int f()':
> t.cpp:4: error: name lookup of 'i' changed for
> new ISO 'for' scoping
> t.cpp:2: error: using obsolete binding at 'i'
>
>A similar thing could be done for (probably
> nontrivial task)
>$ cat t2.cpp
>template struct A { T t; };
>// Swap the follwing 2 functions to get valid C++
>template void foo(const A& data)
>{ foo((int)data.t); }
>
Re: What is wrong with Bugzilla? [Was: Re: GCC and Floating-Point]
--- "Joseph S. Myers" wrote: > On Sun, 29 May 2005, Giovanni Bajo wrote: > > > You are mistaken, we think GCC isn't buggy about > 323 because the C/C++ > > standards do not tell us to do better than this. > If you have higher > > expectations about floating point and C/C++, you > should file a bugreport > > against the C/C++ standards. > > This is ignoring that there are specific > requirements in the C99 standard > regarding the handling of excess precision which we > do not implement, even > with -ffloat-store, which are genuine bugs. > Assignment, casts and > function call and return must discard excess > precision, but we do not > discard excess precision on a cast of an expression > to its own type. > Furthermore, the definition of FLT_EVAL_METHOD for > i386 > > #define TARGET_FLT_EVAL_METHOD \ > (TARGET_MIX_SSE_I387 ? -1 : TARGET_SSE_MATH ? 0 : > 2) > > is wrong when it is 2 because the way the i386 back > end pretends to have > float and double (not just long double) 387 > operations means that > precision may get randomly reduced if an > intermediate value is spilled (so > -1, not 2, is correct). It is also incorrect > because it is an assertion > about both arithmetic and evaluation of constants > and we do not emulate > excess precision when evaluating constants and doing > arithmetic on them. > This makes it *bad* compiler claiming it implements a standard when does not. Giovanni Bajo stop telling lies about what GCC implements. ___ Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com
Re: What is wrong with Bugzilla? [Was: Re: GCC and Floating-Point]
--- Daniel Berlin wrote:
>
> Let's take a duplicate of 323, 21809
>
>
> Compiling the code there with icc gives us:
>
> [EMAIL PROTECTED]:~> icc icca.c
> icca.c(7): warning #1572: floating-point equality
> and inequality
> comparisons are unreliable
> assert(a == x);
> ^
>
> ./[EMAIL PROTECTED]:~> ./a.out
> a.out: icca.c:7: main: Assertion `a == x' failed.
> Aborted
>
> In order to get icc to not generate an executable
> that will abort, you
> have to pass special flags (the same way we have
> -ffloat-store, except I
> believe their -mp flag will just disable any
> optimization that could get
> in the way of this working).
>
> One of these flag options is to tell it to use
> processor specific
> instructions, which auto turns on the equivalent of
> -mfpmath=sse.
>
Here is another case for you try out:
test.c:
#include
#include
volatile float x = 3;
int main()
{
float a = 1 / x;
x = a;
assert(a == x);
printf("a has value of %g \n",a);
printf("x has value of %g \n",x);
assert((int)a == 0);
assert((int)x == 0);
return 0;
}
Compile this gcc {-O0,-O1,-O2,-O3,-Os}
You will notice it will always works (despite not
using -ffloat-store) and not cause an assertion
failure at all.
___
How much free photo storage do you get? Store your holiday
snaps for FREE with Yahoo! Photos http://uk.photos.yahoo.com
Re: What is wrong with Bugzilla? [Was: Re: GCC and Floating-Point]
--- Robert Dewar wrote:
> And so? Why would you expect this particular example
> to give an assertion error. I would not expect an
> assert error here. In unoptimized mode, you
> certainly
> do not expect it, and in optimized mode, I would
> expect the register tracker to know that a and x are
> in the same register at the point of assertion (and
> perhaps even eliminate the comparison entirely).
>
The previous posted case only adds few new lines of
insignificant line of code from:
test-case.c:
#include
volatile float x = 3;
int main()
{
float a = 1 / x;
x = a;
assert(a == x);
}
to
test.c:
#include
#include
volatile float x = 3;
int main()
{
float a = 1 / x;
x = a;
assert(a == x);
printf("a has value of %g \n",a);
printf("x has value of %g \n",x);
assert((int)a == 0);
assert((int)x == 0);
return 0;
}
I would expect the seem behaviour for both cases.
test-case.c cause an assertion failure with
{-O1,-O2,-O3} but test.c does not all.
The first few lines of both case are pretty simalar.
___
Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail
http://uk.messenger.yahoo.com
Re: What is wrong with Bugzilla? [Was: Re: GCC and Floating-Point]
--- Robert Dewar wrote: > Haren Visavadia wrote: > > --- Robert Dewar wrote: > > > I would expect the seem behaviour for both cases. > > why? You have some inaccurate model of computation, > which in the absence of switches, is not guaranteed. > Floating-point semantics are indeed tricky. Why are extra switches added onto the test.c and not test-case.c? ___ Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com
Re: Subversion migration plans
--- Bernardo Innocenti wrote: > Hello, > > browsing the mailing-list archives, I can't find > what's > the current status of the much discussed Subversion > migration. The topic just appears to have been > abandoned > about three months ago. It's not abandoned, it can be found at http://gcc.gnu.org/wiki/SvnPlan ___ How much free photo storage do you get? Store your holiday snaps for FREE with Yahoo! Photos http://uk.photos.yahoo.com
Re: Reporting bugs: there is nothing to gain in frustrating reporters
--- Daniel Berlin wrote: > Again, this is a place where you disagree that this > should be considered > a "bug", but refuse to believe that reasonable > people can disagree on > it. Well, Vincent has given detailed explaination on his views. What do you mean by "reasonable" here? ___ Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com
Re: Reporting bugs: there is nothing to gain in frustrating reporters
--- Andrew Pinski wrote: > Four out of how many? This can not be measured (ie unpredictable), unless you suggesting you are 100% deterministic on every new bug presented to you. ___ How much free photo storage do you get? Store your holiday snaps for FREE with Yahoo! Photos http://uk.photos.yahoo.com
Re: Reporting bugs: there is nothing to gain in frustrating reporters
--- Gabriel Dos Reis wrote: > Vincent Lefevre writes: > > | Other solutions that would fix the bug (but not > ultimate solutions): > | 1) Do not claim that gcc is a conforming ISO C > implementation. > > As far as I can see, there is no such claim. It's implied when using -std=c99 ___ How much free photo storage do you get? Store your holiday snaps for FREE with Yahoo! Photos http://uk.photos.yahoo.com
Re: Some notes on the Wiki
--- Diego Novillo wrote: > And we cannot > do that if we don't have cleared out the copyright > assignment of > wiki content. And so? ___ How much free photo storage do you get? Store your holiday snaps for FREE with Yahoo! Photos http://uk.photos.yahoo.com
Re: Some notes on the Wiki
> --- Diego Novillo wrote: > > Sorry, I don't understand what you're asking. > > > > My line of thought was described in the text that > > you removed: > > "However, it would be very useful for us to > transfer > > information > > from the wiki into the manual from time to time." > > I am suggesting is if the content is on Wiki and not in the manual and you can not get the copyright assignment, there is nothing you can do about it except live with it. In fact, you would be lucky to have the content on Wiki. ___ How much free photo storage do you get? Store your holiday snaps for FREE with Yahoo! Photos http://uk.photos.yahoo.com
Re: Problem compiling libstdc++ is current 4.0.2 cvs (volatile strikes again)
--- Kean Johnston <[EMAIL PROTECTED]> wrote: > System V Release 5 (UnixWare / OpenServer 6). > Your system is NOT supported by GCC, please read http://www.fsf.org/licensing/sco/ ___ How much free photo storage do you get? Store your holiday snaps for FREE with Yahoo! Photos http://uk.photos.yahoo.com
Re: Problem compiling libstdc++ is current 4.0.2 cvs (volatile strikes again)
--- Kean Johnston wrote: > Perhaps you should read README.SCO at the top of the > GCC tree? README.SCO contains: " The GCC team has been urged to drop support for SCO Unix from GCC, as a protest against SCO's irresponsible aggression against free software and GNU/Linux. We have decided to take no action at this time, as we no longer believe that SCO is a serious threat. For more on the FSF's position regarding SCO's attacks on free software, please read: http://www.fsf.org/licensing/sco/ " May be YOU should read it. ___ Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com
Re: Problem compiling libstdc++ is current 4.0.2 cvs (volatile strikes again)
--- Kean Johnston wrote: > > The GCC team has been urged to drop support for > SCO > > Unix from GCC, as a protest against SCO's > irresponsible > > aggression against free software and GNU/Linux. > > We have decided to take no action at this time, > as we > > no longer believe that SCO is a serious threat. > > What part of *NO ACTION* was unclear to you? You missed "The GCC team has been urged to drop support for SCO Unix from GCC, as a protest against SCO's irresponsible aggression against free software". ___ Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com
Re: How to make an application look somewhere other than /lib for ld-linux.so.2
--- Mark Cuss wrote: > > For #1, if I build with --static, then no libraries > can be linked in > dynamically at runtime... I need to do this for > some custom Qt libraries > and plugins, so I can't just make a completely > static executable. This is > unfortunate - the resulting binaries would be big, > but they'd work on any > distro. This is possible by using something like -Wl,-Bdynamic, (insert list of libraries to be dynamically linked),-Bstatic For example, if you want to dynamically link against Qt library and glibc and rest of it being static, you can use -Wl,-Bdynamic,-lqt-mt,-lc,-Bstatic ___ Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com
Re: GCC 4.0.2 Released
--- Ulrich Weigand wrote: > Comparing the cp/ChangeLog files from 4.0.2 and the > 4_0 branch, it looks > like the fix is in the release according to the > current ChangeLog, but > in fact it wasn't: Indeed, http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/cp/init.c.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.412.2.9&r2=1.412.2.10 (the fix) applies cleanly onto the release package. ___ Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com
