My comments are interespersed below...
--- Yann Dirson
reassign 117513 g++-2.95
thanks
On Mon, Oct 29, 2001 at 02:01:55AM -0800, [EMAIL PROTECTED] wrote:
The version of openc++ in unstable will segfault.
Yep.
:(
This happens in driver2.cc::RunSoCompiler(), which:
1. gets a char*
Processing commands for [EMAIL PROTECTED]:
reopen 119440
Bug#119440: g++: Compiler does not give any errors when a function fails to
return required value
Bug reopened, originator not changed.
thanks,
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking
On Wed, Nov 14, 2001 at 02:24:16PM +0200, Eray Ozkural (exa) wrote:
The problem with the above code is that g++ will compile the code as if it is
normal, and when you run it, it will just spew out a random result.
It's YOUR FAULT, not g++'s. It has the capability to warn you of
things like
On Wed, Nov 14, 2001 at 02:24:16PM +0200, Eray Ozkural (exa) wrote:
Not exactly. Here is what I'm talking about:
[...]
int f(int x)
{
int f;
f = 2;
for (int i=1; i=4; i++) {
f = f + i * x;
}
}
[...]
It
might be valid in C++ specification (is it?), but the compiler
I sent this to the debian-ia64 list recently and received no
input. Given the apparent lack of concern about making such a
change, I'd like to inquire on this list whether such a change
would be technically and politically feasible pre-woody.
Matthias, I understand that your input is particularly
Not exactly. Here is what I'm talking about:
I know there are cases that could be detected, like the one you
produce below. However, as soon as you have a function call in the
function, or an operator call, you cannot determine reliably anymore
whether the function will return.
Are you a g++
I believe that Martin and the others are saying that
-Wreturn-type catches this specific problem, but that it is not the
default behaviour because the code is still valid (although the outcome
may not be what the programmer desired). Am I correct?
Close. The code is valid, but that alone
Processing commands for [EMAIL PROTECTED]:
severity 119440 wishlist
Bug#119440: g++: Compiler does not give any errors when a function fails to
return required value
Severity set to `wishlist'.
thanks,
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking
Package: g++
Version: 2.95.4-8
I got an internal compiler error in g++, and since I'm using
a Debian prerelease instead of an official gnu release, I'm sending
my report here. The error occurs when I instatiate a template
which has as one of its members an array whose size is given
by a
On Wed, Nov 14, 2001 at 12:21:27AM -0800, Robert de Forest wrote:
I higly suspect this to be a g++ bug. I tried with g++ 3.0, but it
simply won't compile - any hint to fix it will be appreciated :)
I would be tempted to agree with you, except that it works when built
against libgc5. I'm
10 matches
Mail list logo
