public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
From: Klaus Pedersen <klaus.kruse.pedersen@mail.tele.dk>
To: SID-list <sid@sources.redhat.com>
Subject: Compile problems with GCC 3.0.4
Date: Tue, 23 Apr 2002 16:23:00 -0000	[thread overview]
Message-ID: <3CC5ED29.2060603@mail.tele.dk> (raw)

[-- Attachment #1: Type: text/plain, Size: 552 bytes --]

Hi,

I experience some problems with the current HEAD of sid when
compiling with gcc 3.0.4. Be warned though, this stuff is on the
edge of my c++ knowledge...

* There are a lot of throw() issues.
* A missing deconstructor in mmu/armRemap.cxx
* Some namespace problems in sidcpuutils.h

Sid is configured on my Linux box with:

    CC=gcc-3.0.4 CXX=g++-3.0.4 \
    ac_cv_lib_kernel32_main=no \
    ac_cv_lib_winmm_main=no \
    ../sid/src/configure --prefix=/opt/sid --target=arm-elf

Does my changes make any sense, or is it GCC problems?


BR, Klaus

[-- Attachment #2: sid-fixes-20020424.diff --]
[-- Type: text/plain, Size: 2069 bytes --]

? cvs-update-status
? cvs-update-status2
? cgen/.nautilus-metafile.xml
Index: sid/component/interrupt/arm.h
===================================================================
RCS file: /cvs/src/src/sid/component/interrupt/arm.h,v
retrieving revision 1.2
diff -r1.2 arm.h
18c18
<   ~armIntController() { }
---
>   ~armIntController() throw() { }
Index: sid/component/interrupt/cma222.h
===================================================================
RCS file: /cvs/src/src/sid/component/interrupt/cma222.h,v
retrieving revision 1.1
diff -r1.1 cma222.h
17c17
<   cma222IntController::~cma222IntController() { }
---
>   cma222IntController::~cma222IntController() throw() { }
Index: sid/component/interrupt/components.h
===================================================================
RCS file: /cvs/src/src/sid/component/interrupt/components.h,v
retrieving revision 1.4
diff -r1.4 components.h
87c87
<   virtual ~IntController<bus_size>() { }
---
>   virtual ~IntController<bus_size>() throw() { }
100c100
<     ~interrupt_bus() { }
---
>     ~interrupt_bus() throw() { }
128c128
<     ~interrupt_lines()
---
>     ~interrupt_lines() throw()
Index: sid/component/mapper/compMapper.cxx
===================================================================
RCS file: /cvs/src/src/sid/component/mapper/compMapper.cxx,v
retrieving revision 1.11
diff -r1.11 compMapper.cxx
397c397
< 	   this->selected_accessors.push_back (it);
---
> 	   this->selected_accessors.push_back (&(*it));
Index: sid/component/mmu/armRemap.cxx
===================================================================
RCS file: /cvs/src/src/sid/component/mmu/armRemap.cxx,v
retrieving revision 1.1
diff -r1.1 armRemap.cxx
76a77
>   ~armRemapPause() throw() {};
Index: sid/include/sidcpuutil.h
===================================================================
RCS file: /cvs/src/src/sid/include/sidcpuutil.h,v
retrieving revision 1.18
diff -r1.18 sidcpuutil.h
596c596
< 	cout << t;
---
> 	std::cout << t;
598c598
< 	dynamic_cast <ofstream&> (s) << t;
---
> 	dynamic_cast <std::ofstream&> (s) << t;

             reply	other threads:[~2002-04-23 23:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-23 16:23 Klaus Pedersen [this message]
2002-04-24  7:47 ` Ben Elliston

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3CC5ED29.2060603@mail.tele.dk \
    --to=klaus.kruse.pedersen@mail.tele.dk \
    --cc=sid@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).