From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Eric Dumazet <dada1@cosmosbay.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-m68k@vger.kernel.org,
Roman Zippel <zippel@linux-m68k.org>
Subject: Re: [patch 1/2] m68k: runtime patching infrastructure
Date: Wed, 30 May 2007 09:06:08 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0705300903030.31930@anakin> (raw)
In-Reply-To: <465D1020.3030605@cosmosbay.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: TEXT/PLAIN; charset=UTF-8, Size: 2018 bytes --]
On Wed, 30 May 2007, Eric Dumazet wrote:
> Andrew Morton a écrit :
> > On Mon, 28 May 2007 21:16:31 +0200
> > Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> >
> > > --- a/include/asm-m68k/module.h
> > > +++ b/include/asm-m68k/module.h
> > > @@ -1,7 +1,38 @@
> > > #ifndef _ASM_M68K_MODULE_H
> > > #define _ASM_M68K_MODULE_H
> > > -struct mod_arch_specific { };
> > > +
> > > +struct mod_arch_specific {
> > > + struct m68k_fixup_info *fixup_start, *fixup_end;
> > > +};
> >
> > Here we use struct m68k_fixup_info.
> >
> > > +#define MODULE_ARCH_INIT { \
> > > + .fixup_start = __start_fixup, \
> > > + .fixup_end = __stop_fixup, \
> > > +}
> > > +
> > > #define Elf_Shdr Elf32_Shdr
> > > #define Elf_Sym Elf32_Sym
> > > #define Elf_Ehdr Elf32_Ehdr
> > > +
> > > +
> > > +enum m68k_fixup_type {
> > > + m68k_fixup_memoffset,
> > > +};
> > > +
> > > +struct m68k_fixup_info {
> > > + enum m68k_fixup_type type;
> > > + void *addr;
> > > +};
> >
> > and later we define it.
> >
> > How come it doesn't spit warnings?
> >
> > I think it could be tightened up even if it happens not to warn?
>
>
> struct a {
> struct not_yet_defined *start, *end;
> };
>
> struct not_yet_defined {
> void *foo;
> };
>
> Is a valid and gives no warnings.
I was puzzled by this as well, as there were no compiler warnings...
Apparently you get a warning only if the _first_ occurrence of a struct
is declared inside a parameter list of a function.
So even
struct a {
struct not_yet_defined *start, *end;
};
extern void f(struct not_yet_defined *start);
struct not_yet_defined {
void *foo;
};
doesn't give a warning, because the first occurence is inside the
definition of struct a.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2007-05-30 7:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-28 19:16 [patch 0/2] A few more m68k patches Geert Uytterhoeven
2007-05-28 19:16 ` [patch 1/2] m68k: runtime patching infrastructure Geert Uytterhoeven
2007-05-30 0:38 ` Andrew Morton
2007-05-30 5:48 ` Eric Dumazet
2007-05-30 7:06 ` Geert Uytterhoeven [this message]
2007-05-30 8:20 ` Joerg Dorchain
2007-05-30 11:19 ` Geert Uytterhoeven
2007-05-30 11:40 ` Joerg Dorchain
2007-05-30 8:23 ` Andreas Schwab
2007-05-30 18:03 ` Linus Torvalds
2007-06-03 15:56 ` Wouter Verhelst
2007-05-28 19:16 ` [patch 2/2] m68k: Discontinuous memory support Geert Uytterhoeven
2007-05-30 0:44 ` Andrew Morton
2007-05-30 0:45 ` Andrew Morton
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=Pine.LNX.4.64.0705300903030.31930@anakin \
--to=geert@linux-m68k.org \
--cc=akpm@linux-foundation.org \
--cc=dada1@cosmosbay.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=zippel@linux-m68k.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®