This is the mail archive of the gcc-bugs@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]

[Bug target/45250] [4.6 Regression] FAIL: tr1/5_numerical_facilities/special_functions/01_assoc_laguerre/check_nan.cc



------- Comment #8 from dave at hiauly1 dot hia dot nrc dot ca  2010-09-01 22:11 -------
Subject: Re:  [4.6 Regression] FAIL:
        tr1/5_numerical_facilities/special_functions/01_assoc_laguerre/check
        _nan.cc

On Tue, 31 Aug 2010, jakub at gcc dot gnu dot org wrote:

> 
> 
> ------- Comment #7 from jakub at gcc dot gnu dot org  2010-08-31 19:48 -------
> Created an attachment (id=21614)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21614&action=view)
>  --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21614&action=view)
> gcc46-pr45250.patch
> 
> The problem is that the PA backend has quite lame setup, where
> FRAME_POINTER_REGNUM is the same as HARD_FRAME_POINTER_REGNUM and
> ARG_POINTER_REGNUM, thus the replacements var-tracking is doing in order to
> decrease size of loclists and use DW_OP_fbreg where possible, aren't reliable,
> as the testcase shows, because the same hard register can be used for arbitrary
> other data.  The following patch fixes it by not doing the replacements on PA
> and similar targets at all when doing VALUE based var-tracking.  Ideally PA
> backend would be fixed up to use different (fixed) hard regno, made up and
> always eliminated, for FRAME_POINTER_REGNUM.

The change fixes the PR on hppa-unknown-linux-gnu.  I'll look at
implementing the above this weekend.

Thanks very much for looking at this problem.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45250


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