public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jim Wilson <wilson@cygnus.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Unwind problem for __attribute__ noreturn
Date: Wed, 21 Mar 2001 00:24:23 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590693005307@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005303@msgid-missing>

I'm not able to understand any of this.

I'm not a kernel expert.  It has been months since I've booted a kernel that
I built, and much longer since I've booted a kernel that included kdb.
I do not know what the kernel uses the unwind info for.  This question has
been asked on this list by others recently and has not been answered.
If I have to reproduce this problem by building a kernel and running kdb,
then you will have a very long wait before I look at this, since I will fix
everything I know how to fix first.

The comment about "control reaches end of non-void function" warnings doesn't
make sense.  panic() is defined as returning void, so it should not be possible
to get this warning.  I downloaded 2.4.2 today just to be sure, along with
David's 010228 patch.

I tried deleting the NORET_TYPE from the .c file, but I get identical .i
with and without it (disregarding whitespace).  It doesn't seem to do anything.
I tried deleting the noreturn attribute that came from the kernel.h header
file, but doesn't do anything either.  I get identical .s files with or
without it.

If you want me to look at this, you will have to give me something I can
understand.  Preferably a .i file and a gcc command.  But if you want me
to look at a kernel, then you need to tell me what kernel you are using,
what patches you have applied to it, where you got the patches from,
what kernel config file you are using, and what compiler version you are using.
And possibly other stuff that I don't know yet that I need.

I have linux-2.4.2 and David's 010228 patch.  I am looking at the function
panic() in the kernel/panic.c file.  I am using current FSF gcc development
sources.

The only thing that occurs to me at the moment is that maybe the kdb patch
is doing something here that causes the problem.  I've never downloaded the
kdb patch.  Last time I used kdb, it was still part of the ia64-linux kernel
sources.  If I need the kdb patch, where to I get it from?

Jim


  reply	other threads:[~2001-03-21  0:24 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-20  2:10 [Linux-ia64] Unwind problem for __attribute__ noreturn Keith Owens
2001-03-21  0:24 ` Jim Wilson [this message]
2001-03-21  6:03 ` Keith Owens
2001-03-21  6:53 ` David Mosberger
2001-03-21  7:12 ` Jim Wilson
2001-03-21  7:54 ` David Mosberger
2001-03-21  8:54 ` Keith Owens
2001-03-21 17:54 ` David Mosberger
2001-03-21 18:48 ` Cary Coutant
2001-03-21 19:07 ` Jim Wilson
2001-03-21 19:13 ` David Mosberger
2001-03-21 19:13 ` Jim Wilson
2001-03-21 19:26 ` Cary Coutant
2001-03-21 19:40 ` Jim Wilson
2001-03-21 19:58 ` David Mosberger
2001-03-21 20:00 ` Jim Wilson
2001-03-21 20:38 ` Jim Wilson
2001-03-21 22:54 ` David Mosberger
2001-03-21 23:42 ` Cary Coutant
2001-03-22 17:00 ` Rich Altmaier
2001-03-23 20:28 ` Jim Wilson
2001-03-24  0:58 ` Cary Coutant
2001-03-24  1:27 ` Keith Owens
2001-03-24  1:37 ` Jim Wilson
2001-03-26 22:06 ` DE-DINECHIN,CHRISTOPHE (HP-Cupertino,ex1)
2001-03-26 22:58 ` Cary Coutant

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=marc-linux-ia64-105590693005307@msgid-missing \
    --to=wilson@cygnus.com \
    --cc=linux-ia64@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