From: Ralf Baechle <ralf@mailhost.uni-koblenz.de>
To: davem@jenolan.rutgers.edu (David S. Miller)
Cc: ralf@mailhost.uni-koblenz.de, linux@cthulhu.engr.sgi.com,
linux-mips@fnet.fr
Subject: Re: Fun with binutils ...
Date: Wed, 16 Jul 1997 00:15:15 +0200 (MET DST) [thread overview]
Message-ID: <199707152215.AAA20071@informatik.uni-koblenz.de> (raw)
In-Reply-To: <199707151948.PAA08407@jenolan.rutgers.edu> from "David S. Miller" at Jul 15, 97 03:48:12 pm
> - GAS still doesn't deal with _huge_ loops. The only program I know
> of which is affected is lmbench, but that alone is reason enough
> to fix it :-)
>
> It is not a bug, just that we have the local label semantics specified
> for linux-mips differently in gcc and gas. I fixed this ages ago and
> it made lat_ctx.c compile just fine.
It has nothing to do with local label semantics of GCC; I can easily trigger
the problem in plain assembler using local or nonlocal labels. Maybe you
were still using a non-PIC lat_ctx at that time? The problem only affects
PIC. Another explanation would be that the size of the cacheflushing
loop in lmbench was somewhen increased or the GCC variant you used generates
different branches. The problematic GAS code from:
binutils/gas/config/tc-mips.c:
[...]
3439 case M_BGTL_I:
3440 likely = 1;
3441 case M_BGT_I:
[...]
3470 if (imm_expr.X_op != O_constant)
3471 as_bad ("Unsupported large constant");
[...]
3536 case M_BGTUL_I:
3537 likely = 1;
3538 case M_BGTU_I:
[...]
3544 if (imm_expr.X_op != O_constant)
3545 as_bad ("Unsupported large constant");
[...]
3632 case M_BLEL_I:
3633 likely = 1;
3634 case M_BLE_I:
[...]
3647 if (imm_expr.X_op != O_constant)
3648 as_bad ("Unsupported large constant");
[...]
3694 case M_BLEUL_I:
3695 likely = 1;
3696 case M_BLEU_I:
[...]
3702 if (imm_expr.X_op != O_constant)
3703 as_bad ("Unsupported large constant");
Ralf
WARNING: multiple messages have this Message-ID (diff)
From: Ralf Baechle <ralf@mailhost.uni-koblenz.de>
To: "David S. Miller" <davem@jenolan.rutgers.edu>
Cc: ralf@mailhost.uni-koblenz.de, linux@cthulhu.engr.sgi.com,
linux-mips@fnet.fr
Subject: Re: Fun with binutils ...
Date: Wed, 16 Jul 1997 00:15:15 +0200 (MET DST) [thread overview]
Message-ID: <199707152215.AAA20071@informatik.uni-koblenz.de> (raw)
Message-ID: <19970715221515.pxjWCxwGvNmarPimeBigKBs1zxXqmLvWUU5yWKVWmBc@z> (raw)
In-Reply-To: <199707151948.PAA08407@jenolan.rutgers.edu> from "David S. Miller" at Jul 15, 97 03:48:12 pm
> - GAS still doesn't deal with _huge_ loops. The only program I know
> of which is affected is lmbench, but that alone is reason enough
> to fix it :-)
>
> It is not a bug, just that we have the local label semantics specified
> for linux-mips differently in gcc and gas. I fixed this ages ago and
> it made lat_ctx.c compile just fine.
It has nothing to do with local label semantics of GCC; I can easily trigger
the problem in plain assembler using local or nonlocal labels. Maybe you
were still using a non-PIC lat_ctx at that time? The problem only affects
PIC. Another explanation would be that the size of the cacheflushing
loop in lmbench was somewhen increased or the GCC variant you used generates
different branches. The problematic GAS code from:
binutils/gas/config/tc-mips.c:
[...]
3439 case M_BGTL_I:
3440 likely = 1;
3441 case M_BGT_I:
[...]
3470 if (imm_expr.X_op != O_constant)
3471 as_bad ("Unsupported large constant");
[...]
3536 case M_BGTUL_I:
3537 likely = 1;
3538 case M_BGTU_I:
[...]
3544 if (imm_expr.X_op != O_constant)
3545 as_bad ("Unsupported large constant");
[...]
3632 case M_BLEL_I:
3633 likely = 1;
3634 case M_BLE_I:
[...]
3647 if (imm_expr.X_op != O_constant)
3648 as_bad ("Unsupported large constant");
[...]
3694 case M_BLEUL_I:
3695 likely = 1;
3696 case M_BLEU_I:
[...]
3702 if (imm_expr.X_op != O_constant)
3703 as_bad ("Unsupported large constant");
Ralf
next prev parent reply other threads:[~1997-07-15 22:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-07-15 19:35 Fun with binutils Ralf Baechle
1997-07-15 19:48 ` David S. Miller
1997-07-15 22:15 ` Ralf Baechle [this message]
1997-07-15 22:15 ` Ralf Baechle
-- strict thread matches above, loose matches on Subject: below --
1997-07-18 15:20 Angus MacCuish
1997-07-18 15:20 ` Angus MacCuish
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=199707152215.AAA20071@informatik.uni-koblenz.de \
--to=ralf@mailhost.uni-koblenz.de \
--cc=davem@jenolan.rutgers.edu \
--cc=linux-mips@fnet.fr \
--cc=linux@cthulhu.engr.sgi.com \
/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