public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: Joel Sherrill <joel.sherrill@OARcorp.com>
Cc: gcc@gcc.gnu.org
Subject: Re: mcore-elf on 3.3 branch
Date: Tue, 13 May 2003 17:23:00 -0000	[thread overview]
Message-ID: <m3r8726a37.fsf@redhat.com> (raw)
In-Reply-To: <3EBFDFB0.72DD73FC@OARcorp.com> (Joel Sherrill's message of "Mon, 12 May 2003 12:53:52 -0500")

Hi Joel,

> mcore-elf has a problem on the 3.3 branch.  I currently have a 
> cc1 running with over 17 minutes CPU time on a 2.4 Ghz P4 
> compiling _lshrdi3.o.

Still investigating.  Problem is in the second if-conversion pass.
Applying the workaround patch below allows the compiler to build, (and
possibly bootstrap, I have not checked).

Cheers
        Nick

2003-05-13  Nick Clifton  <nickc@redhat.com>

	* config/mcore/mcore.h (OPTIMIZATION_OPTIONS): Disable second
	if-conversion pass.

Index: gcc/config/mcore/mcore.h
===================================================================
RCS file: /cvs/gcc/gcc/gcc/config/mcore/mcore.h,v
retrieving revision 1.41.4.1
diff -c -3 -p -w -r1.41.4.1 mcore.h
*** gcc/config/mcore/mcore.h	29 Apr 2003 14:31:53 -0000	1.41.4.1
--- gcc/config/mcore/mcore.h	13 May 2003 17:20:52 -0000
*************** extern const char * mcore_stack_incremen
*** 194,199 ****
--- 194,200 ----
      {						\
        flag_no_function_cse = 1;			\
        flag_omit_frame_pointer = 1;		\
+       flag_if_conversion2 = 0; \
  						\
        if (LEVEL >= 2)				\
          {					\
        

  reply	other threads:[~2003-05-13 17:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-12 18:03 Joel Sherrill
2003-05-13 17:23 ` Nick Clifton [this message]
2003-05-13 18:39 ` Nick Clifton

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=m3r8726a37.fsf@redhat.com \
    --to=nickc@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=joel.sherrill@OARcorp.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).