public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrzej Krzysztofowicz <kufel!ankry@green.mif.pg.gda.pl>
To: kufel!infradead.org!dwmw2@green.mif.pg.gda.pl (David Woodhouse)
Cc: kufel!svgalib.org!matan@green.mif.pg.gda.pl (Matan Ziv-Av),
	kufel!arm.linux.org.uk!rmk@green.mif.pg.gda.pl (Russell King),
	kufel!csd.uoc.gr!papadako@green.mif.pg.gda.pl (mythos),
	kufel!vger.kernel.org!linux-kernel@green.mif.pg.gda.pl
Subject: Re: Can't compile 2.4.3 with agcc
Date: Tue, 24 Apr 2001 00:32:52 +0200 (CEST)	[thread overview]
Message-ID: <200104232232.AAA12700@kufel.dom> (raw)
In-Reply-To: <2835.988060565@redhat.com> from "David Woodhouse" at kwi 23, 2001 10:16:05

> It's known at compile time, but not at preprocessing time, so it can't be 
> done with #error. If you can come up with a way of doing it at compile time 
> such that:
> 
>  1. It's _guaranteed_ to work when the compiler does align the members 
> 	of the structure as we desire.
>  2. It gives a message sufficiently informative that it prevents further
> 	such reports getting to l-k.

So maybe make the original error message more informative ?
Just something like:

-             extern void __buggy_fxsr_alignment(void);
-             __buggy_fxsr_alignment();
+             extern void __BUG__task_struct__data_is_not_properly_alligned__Probably_your_compiler_is_buggy(void);
+             __BUG__task_struct__data_is_not_properly_alligned__Probably_your_compiler_is_buggy();

Andrzej

  reply	other threads:[~2001-04-23 22:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-23 13:13 Can't compile 2.4.3 with agcc mythos
2001-04-23 14:48 ` Russell King
2001-04-23 15:27 ` Alan Cox
2001-04-23 15:52 ` David Woodhouse
2001-04-23 17:57   ` Ingo Oeser
2001-04-23 19:43   ` Alan Cox
2001-04-23 20:46     ` David Woodhouse
2001-04-23 21:03   ` Matan Ziv-Av
2001-04-23 21:16     ` David Woodhouse
2001-04-23 22:32       ` Andrzej Krzysztofowicz [this message]
2001-04-23 22:54         ` David Woodhouse
2001-04-24  8:53           ` Russell King
2001-04-24 12:37           ` David Woodhouse
2001-04-23 22:25   ` Horst von Brand
2001-04-23 22:35     ` David Woodhouse
2001-04-24 13:28       ` Horst von Brand
2001-04-24 13:30         ` David Woodhouse

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=200104232232.AAA12700@kufel.dom \
    --to=kufel!ankry@green.mif.pg.gda.pl \
    --cc=kufel!arm.linux.org.uk!rmk@green.mif.pg.gda.pl \
    --cc=kufel!csd.uoc.gr!papadako@green.mif.pg.gda.pl \
    --cc=kufel!infradead.org!dwmw2@green.mif.pg.gda.pl \
    --cc=kufel!svgalib.org!matan@green.mif.pg.gda.pl \
    --cc=kufel!vger.kernel.org!linux-kernel@green.mif.pg.gda.pl \
    /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