This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: How to inline a huge m68k code?

From: ami_stuff <ami_stuff at o2 dot pl>
To: Andrew Haley<aph at redhat dot com>
Cc: gcc-help at gcc dot gnu dot org
Date: Mon, 13 Jul 2009 16:33:06 +0200
Subject: Re: How to inline a huge m68k code?
References: <792d79d7.6fd9f7d1.4a5a55eb.b3c4b@o2.pl> <4A5B42CC.4060109@redhat.com> <1f1a1a96.2b44fde2.4a5b4341.e40d1@o2.pl> <4A5B43FA.90206@redhat.com>

> > Ok, so it is a GCC's bug?
> 
> It's perhaps an optimization that gcc doesn't do.  But then
> there is an infinite number of optimizations that gcc doesn't do.

How should I modify GCC's inline to repleace MULH function (to make it compatible)?
I will copy & paste the code to FFmpeg's source and do the benchmark with FFmpeg.

Follow-Ups:
- Re: How to inline a huge m68k code?
  - From: Andrew Haley

References:
- How to inline a huge m68k code?
  - From: ami_stuff
- Re: How to inline a huge m68k code?
  - From: Andrew Haley
- Re: How to inline a huge m68k code?
  - From: ami_stuff
- Re: How to inline a huge m68k code?
  - From: Andrew Haley

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]