public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bernd Roesch <nospamname@gmx.de>
To: ami_stuff <ami_stuff@o2.pl>, 	Martin Guy <martinwguy@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: "-fno-unswitch-loops" option have no effect?
Date: Mon, 17 Aug 2009 19:42:00 -0000	[thread overview]
Message-ID: <yam11551.552.283353120@mail.gmx.net> (raw)
In-Reply-To: <3165a1e6.6c5afa14.4a89378f.5d332@o2.pl>

Hello ami_stuff

On 17.08.09, you wrote:

> Hi,
> 
>> Hundreds and hundreds of people read this list, so every low-detail
>> "I think there may be a bug" message you send wastes hours of other
>> people's time.
> 
> Ok, Ok, but if someone will reproduce the same problem on his system I can
> fill bugreport, otherwise I will only waste my time, hours of my time, to
> start detailed bugreport. Maybe this is only fault of my GCC's build?

gcc > 4 AOS 68k builds are build from offical gcc sourcetree and there are
no changes 


> 
>> If it *is* a bug, on the bug tracker, it will be picked up by people
>> interested in that specific area
> 
> It may takes months before someone will look at the bugreport. If it's
> really a bug IMHO it's a bit critical bug.
> 
>> though you don't seem to do much
>> in-depth research, nor do you supply any detail of what you did and
>> what you expected.
> 
> There is no need for much detail, just compile any bigger sourcecode with
> -O3 -fno-.. and after that with -O2 .... When the object files are not
> identical, something is wrong and I can start a bug report.

how much is size diffrent ?

You use
-finline-functions -fpredictive-commoning -fgcse-after-reload
-ftree-vectorize 

right ?

I see in Gcc source that there is more set on -O3.
 flag_ipa_cp_clone = opt3;
  if (flag_ipa_cp_clone)
    flag_ipa_cp = 1; 

.but i
think you can easy test, compile the ffmpeg, if it give no internal
compiler error with -fno........ then it work.

here is from source opt.c what is set on opt3

opt3 = (optimize >= 3); 
flag_predictive_commoning = opt3;
  flag_inline_functions = opt3;
  flag_unswitch_loops = opt3;
  flag_gcse_after_reload = opt3;
  flag_tree_vectorize = opt3;
  flag_ipa_cp_clone = opt3;
  if (flag_ipa_cp_clone)
    flag_ipa_cp = 1; 



> 
> Regards
> 
Regards

  reply	other threads:[~2009-08-17 18:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-17  7:19 ami_stuff
     [not found] ` <56d259a00908170344v54442954u3a5d0337de3b98fe@mail.gmail.com>
2009-08-17 13:29   ` ami_stuff
2009-08-17 19:42     ` Bernd Roesch [this message]
2009-08-17 19:54       ` ami_stuff
2009-08-17 22:16       ` Alexander Strange
2009-08-17 13:33 ` Richard Guenther
2009-08-17 13:35   ` ami_stuff
2009-08-17 16:01     ` Paolo Bonzini
2009-08-17 16:07       ` ami_stuff
2009-08-17 16:14         ` Paolo Bonzini

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=yam11551.552.283353120@mail.gmx.net \
    --to=nospamname@gmx.de \
    --cc=ami_stuff@o2.pl \
    --cc=gcc@gcc.gnu.org \
    --cc=martinwguy@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).