public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Naveen Sharma, Noida" <naveens@noida.hcltech.com>
To: amylaar@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: target/9594: [3.3/3.4 regression] [sh4-elf] Assembler complai ns pcrel too far.
Date: Tue, 29 Apr 2003 06:56:00 -0000	[thread overview]
Message-ID: <20030429065600.9290.qmail@sources.redhat.com> (raw)

The following reply was made to PR target/9594; it has been noted by GNATS.

From: "Naveen Sharma, Noida" <naveens@noida.hcltech.com>
To: amylaar@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
        nobody@gcc.gnu.org,
        "Sanjiv Kumar Gupta, Noida"
	 <sanjivg@noida.hcltech.com>,
        gcc-gnats@gcc.gnu.org
Cc: kkojima@gcc.gnu.org, aoliva@redhat.com
Subject: Re: target/9594: [3.3/3.4 regression] [sh4-elf] Assembler complai
	ns pcrel too far.
Date: Tue, 29 Apr 2003 12:09:27 +0530

 Hi,
  
 > Synopsis: [3.3/3.4 regression] [sh4-elf] Assembler complains 
 > pcrel too far.
 > 
 > Responsible-Changed-From-To: unassigned->amylaar
 > Responsible-Changed-By: amylaar
 > Responsible-Changed-When: Mon Apr 28 13:07:29 2003
 > Responsible-Changed-Why:
 >     Because I fixed this problem.
 > State-Changed-From-To: open->feedback
 > State-Changed-By: amylaar
 > State-Changed-When: Mon Apr 28 13:07:29 2003
 > State-Changed-Why:
 >     Fixed on 15th April in mainline and 3.3 branch.
 > 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&
 > database=gcc&pr=9594
 
 Thanks, 
 The patch fixes the problem. So this PR may be closed
 
 On a related note, I notice that gcc is known to generate 
 out of bound branches for SH.
 
 http://gcc.gnu.org/ml/gcc-patches/2002-01/msg00818.html
 http://gcc.gnu.org/ml/gcc-bugs/2002-06/msg00896.html
 
 From the discussion thread following the latter, it seems 
 there needs to be some design changes to solve these sort 
 of problems. In this message
  http://gcc.gnu.org/ml/gcc-patches/2002-11/msg00192.html
 
 You suggest to "marry" the local constant pool generation 
 with an early branch shortening pass.
 
 I would like to analyse this more, and implement it, if this can 
 avoid problems of this nature. What do you think ?
 
 Best Regards,
   Naveen Sharma.


                 reply	other threads:[~2003-04-29  6:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030429065600.9290.qmail@sources.redhat.com \
    --to=naveens@noida.hcltech.com \
    --cc=amylaar@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.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 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).