From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: netfilter-devel@lists.netfilter.org
Cc: Linux Networking Development Mailing List <netdev@oss.sgi.com>
Subject: ipt_physdev.c alignment problems on parisc64
Date: Tue, 2 Sep 2003 11:30:50 -0300 [thread overview]
Message-ID: <20030902143050.GC3398@conectiva.com.br> (raw)
The 1.786.1.54 changeset (i.e. the initial ipt_physdev.c one 8) created this
alignment problems on parisc64:
tmp.stdout.allegro.31506.s: Assembler messages:
tmp.stdout.allegro.31506.s:97: Error: Field not properly aligned [8] (18).
tmp.stdout.allegro.31506.s:97: Error: Invalid operands
tmp.stdout.allegro.31506.s:125: Error: Field not properly aligned [8] (34).
tmp.stdout.allegro.31506.s:125: Error: Invalid operands
tmp.stdout.allegro.31506.s:129: Error: Field not properly aligned [8] (50).
tmp.stdout.allegro.31506.s:129: Error: Invalid operands
I got this nailed to the match function, on these lines:
for (i = 0, ret = 0; i < IFNAMSIZ/sizeof(unsigned long); i++) {
ret |= (((const unsigned long *)indev)[i]
^ ((const unsigned long *)info->physindev)[i])
& ((const unsigned long *)info->in_mask)[i];
}
and
for (i = 0, ret = 0; i < IFNAMSIZ/sizeof(unsigned long); i++) {
ret |= (((const unsigned long *)outdev)[i]
^ ((const unsigned long *)info->physoutdev)[i])
& ((const unsigned long *)info->out_mask)[i];
}
Reading specs from /opt/palinux/lib/gcc-lib/hppa64-linux/3.0.4/specs
Configured with: ../../gcc-3.0-3.0.4ds3/src/configure --host=hppa-linux --build=hppa-linux --target=hppa64-linux --disable-shared --disable-nls --enable-languages=c --prefix=/opt/palinux
Thread model: single
gcc version 3.0.4
acme@allegro:~/bk/scsi-2.6$
- Arnaldo
next reply other threads:[~2003-09-02 14:30 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-02 14:30 Arnaldo Carvalho de Melo [this message]
2003-09-02 19:16 ` ipt_physdev.c alignment problems on parisc64 Bart De Schuymer
2003-09-02 20:03 ` Arnaldo Carvalho de Melo
2003-09-04 3:04 ` David S. Miller
2003-09-05 15:31 ` Harald Welte
2003-09-09 2:14 ` David S. Miller
2003-09-13 19:59 ` Bart De Schuymer
2003-09-14 2:25 ` David S. Miller
2003-09-15 22:59 ` David S. Miller
2003-09-16 6:05 ` Bart De Schuymer
2003-09-16 6:02 ` David S. Miller
2003-09-16 9:18 ` Henrik Nordstrom
2003-09-16 14:09 ` Harald Welte
2003-09-17 1:16 ` David S. Miller
2003-09-17 21:17 ` Bart De Schuymer
2003-09-19 2:48 ` David S. Miller
2003-09-20 11:32 ` Bart De Schuymer
2003-09-20 16:05 ` Arnaldo Carvalho de Melo
2003-09-22 0:53 ` David S. Miller
2003-09-16 14:06 ` Harald Welte
2003-09-16 15:15 ` Tom Marshall
2003-09-16 15:57 ` Bart De Schuymer
2003-09-17 1:23 ` David S. Miller
2003-09-17 6:42 ` Bart De Schuymer
2003-09-17 6:56 ` David S. Miller
2003-09-12 1:40 ` jamal
2003-09-12 8:56 ` Harald Welte
2003-09-12 10:56 ` Oskar Andreasson
2003-09-12 12:56 ` jamal
2003-09-12 13:55 ` Oskar Andreasson
2003-09-12 12:54 ` jamal
2003-09-20 5:50 ` Harald Welte
2003-09-21 13:57 ` ppp ifindex WAS(Re: " jamal
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=20030902143050.GC3398@conectiva.com.br \
--to=acme@conectiva.com.br \
--cc=netdev@oss.sgi.com \
--cc=netfilter-devel@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.