mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Frank <mflt1@micrologica.com.hk>
To: linux-kernel@vger.kernel.org
Subject: [Swsusp] internal compiler error - gcc3.2 confirmed
Date: Fri, 4 Apr 2003 21:42:16 +0800	[thread overview]
Message-ID: <200304042142.16795.mflt1@micrologica.com.hk> (raw)

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



[-- Attachment #2: Robert Woerle Paceblade/Support <robert@paceblade.com>: Re: [Swsusp] internal compiler error --]
[-- Type: message/rfc822, Size: 3894 bytes --]

From: Robert Woerle Paceblade/Support <robert@paceblade.com>
To: swsusp@lister.fornax.hu
Subject: Re: [Swsusp] internal compiler error
Date: Fri, 04 Apr 2003 15:01:45 +0200
Message-ID: <3E8D8239.8030901@paceblade.com>

i found that suse 8.2
uses gcc 3.3 (prerelease )

which doesnt sound too stable to me ...
i also have problems with ide-cd to compile .. and i get huge warninigs 
like

cdrom_buffer_sectors':
ide-cd.c:816: warning: comparison between signed and unsigned
ide-cd.c:816: warning: signed and unsigned type in conditional expression


in almost every module .....

Can somebody help installing a gcc 3.1 or even 2.95 parallel to the one 
i have here ???
i remmeber there was a way where i only needed to change some EXPORTS 
when i wanted to cchoose the gcc !!!

Rob

Robert Woerle Paceblade/Support schrieb:

> now i get this when i try to compile 2.4.20 with any swsusp patch !! ( 
> tried , beta19 and beta19-14 and beta19-16)
>
> the thing i changed is that i now use Suse 8.2 and before i had suse 
> 8.1 and everything was fine .
>
> i dont know if there is a gcc differenc between those 2 but it looks 
> like !!
>
> Cheers Rob
>
>
>
> cc -D__KERNEL__ -I/usr/src/linux-2.4.20/include -Wall 
> -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing 
> -fno-common -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 
> -march=i686 -malign-functions=0 -malign-jumps=0 -malign-loops=0   
> -nostdinc -iwithprefix include -DKBUILD_BASENAME=sched  
> -fno-omit-frame-pointer -c -o sched.o sched.c
> cc1: warning: -malign-loops is obsolete, use -falign-loops
> cc1: warning: -malign-jumps is obsolete, use -falign-jumps
> cc1: warning: -malign-functions is obsolete, use -falign-functions
> sched.c: In function `schedule':
> sched.c:611: warning: comparison between signed and unsigned
> sched.c:640: warning: comparison between signed and unsigned
> sched.c:709: internal compiler error: in merge_assigned_reloads, at 
> reload1.c:6133
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
>

-- 
_____________________________________
*Robert Woerle
**Technical Support | Linux
PaceBlade Technology Europe SA*
phone: 	+49 89 552 99935
fax: 	+49 89 552 99910
mobile: 	+49 179 474 45 27
email: 	robert@paceblade.com <mailto:robert@paceblade.com>
web: 	http://www.paceblade.com
_____________________________________






_______________________________________________
swsusp mailing list
swsusp@lister.fornax.hu
http://lister.fornax.hu/mailman/listinfo/swsusp


                 reply	other threads:[~2003-04-04 13:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200304042142.16795.mflt1@micrologica.com.hk \
    --to=mflt1@micrologica.com.hk \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®