Package: g++-2.95
Version: 1:2.95.4-19
When combine working with int32 and int64, not all operations performed
correctly.
Here is code example
=begin
#include stdint.h
#include stdio.h
#include iostream
int main()
{
const long int offset = 1025;
FILE* F = fopen(samplefile, r);
Package: g++-2.95
Version: 1:2.95.4-19
When combine working with int32 and int64, not all operations performed
correctly.
Here is code example
=begin
#include stdint.h
#include stdio.h
#include iostream
int main()
{
const long int offset = 1025;
FILE* F = fopen(samplefile, r);
Please delete this bug as this report does not contain kernal and libc info.
There is a duplicate bug 222377 which does.
On Wed, Aug 21, 2002 at 11:55:27AM +0300, Alexei Khlebnikov wrote:
I think this program should not terminate at all because i will
always be one greater than oldi.
I think gcc3.0 has a problem with no optimization then but since
there is later version that works gcc 3.1.1, upgrade
When g++ 3.2 becomes the next Debian compiler, it will be necessary to
recompile a lot of packages. Also, it will be necessary to have the
old binary packages, and their shared libraries, coexist.
Is there a specific plan to implement this coexistence? I can think of
the following
On Tue, 29 Jan 2002 14:31:03 -0500
Daniel Jacobowitz [EMAIL PROTECTED] wrote:
DJ You should add swap space in that case. And:
Note that /etc/security/limits.conf contains these lines:
*harddata10
*hardrss 10
*hard
On Fri, 25 Jan 2002 08:22:18 +0100
J.H.M. Dassen (Ray) [EMAIL PROTECTED] wrote:
JD( [Please do not use HTML in email. This is email, not the web]
JD( On Fri, Jan 25, 2002 at 16:57:10 +1300, Etienne Le Sueur wrote:
I have recently tried to install g++, using dpkg. When I do so, dpkg
reports a
On Wed, 16 Jan 2002 13:36:47 +0300
ALEXANDER SHISHCKIN [EMAIL PROTECTED] wrote:
AS Hi everyone!
AS Here's my trouble: a few days ago I've upgraded gcc
AS to 3.0 and the package name no longer looks like 'gcc',
AS but 'gcc-3.0'.
AS Now other packages depending on 'gcc' fail to install.
AS What
On Mon, 14 Jan 2002 14:31:04 +0300
ALEXANDER SHISHCKIN [EMAIL PROTECTED] wrote:
AS I got trouble when upgrading from GCC 2.95 to 3.0.3.
AS None of the programs are working with it saying that
AS GNU C compiler can make binaries or so.
AS Where can I get info on fixing this?
Please describe your
Ugh, sorry for late answer. I was ill and thinked about this subject.
Martin v. Loewis wrote:
Please answer somebody wether it is a bug and wether I should submit it to
GNATS.
I believe this is not a bug, because there are no const-qualified
function types in C++.
If you don't agree,
Suryakant wrote:
Can anyone please point me where I can get installabel gcc compiler
(gcc 2.9.1 . or later but stable )
You can get any release you want from http://gcc.gnu.org.
Hello, maintainers.
I don't know what the package has the bug, so I write to 3 maintainers
(packages: menu, dwww, libstdc++3-doc).
I have the following versions of these packages installed on my system:
ii menu 2.1.5-10 provides update-menus functions for some app
ii dwww
Martin v. Loewis wrote:
When compiling the same programs with these compilers, g++ 2.95 is
much (sometimes 3 times) faster than g++ 3.0, even without
optimizing (without -O).
Not sure what you asking. Are you saying g++ 2.95 is faster, or that
the generated code is faster?
Why is it
Hello all.
When compiling the same programs with these compilers, g++ 2.95 is much
(sometimes 3 times) faster than g++ 3.0, even without optimizing (without -O).
Why is it happening? Is it so because of more complex templates in recent
libstdc++?
Is g++ 3.0 really a step further ?
Regards,
Zoltan Nagy wrote:
When I use the g++-3.0 ( gcc version 3.0.2 20010922 (Debian prerelease)
) the compiler doesn't link the libstdc++. It might be a bug.
Firstly, the compiler does not link at all. It is linker's task.
Secondly, the linker links it [libstdc++] fine for me (g++ is the same
Martin v. Loewis wrote:
Probably, I've found an error in libstdc++. I can't catch out_of_range
exception.
This is not a bug in the library, but in your code. You need to
include stdexcept before using out_of_range.
Thank you very much for explaining.
My appologies to you and all the
G++ emits strange warning. It is really annoying me, because I include similar
header to many files.
This is the code.
=== begin ===
template class _TTN, class _TNK
class A
{
//public:
private:
typedef _TTN _TN;
};
template class _NY, class _TN
class B : virtual public A _TN, _NY
{
_TN func ()
Martin v. Loewis wrote:
I think so. I fail to see the bug in your report, though. Your code is
illegal (or, rather, ill-formed - some GNU coding style advises us not
to claim that you are breaking the law by writing the code).
template class _TW, class _TTWO
struct SGBMb : public SGBb _TW
Hello all.
I am faced with a problem: my classes hierarchy is not compiled by G++ 3.0
Debian prerelease.
I use woody branch and I don't want to switch to sid because I want to have a
somewhat stable system.
G++ 3.0 Debian prerelease ICEs on my (legal) code. I've wrote a bug report to
GNATS and
19 matches
Mail list logo
