From: Joel Brobecker <brobecker@adacore.com>
To: Walfred Tedeschi <walfred.tedeschi@intel.com>
Cc: qiyaoltc@gmail.com, "Heckel,
Bernhard" <bernhard.heckel@intel.com>,
keven.boell@linux.intel.com,
gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/2] fort_dyn_array: add basic fortran dyn array support
Date: Tue, 09 Feb 2016 11:36:00 -0000 [thread overview]
Message-ID: <20160209113615.GE15342@adacore.com> (raw)
In-Reply-To: <56B89C78.9050808@intel.com>
> I don't think I will be able to fix the failures on the mentioned
> hosts/targets before you
> create the branch, as I need to replicate the environment on my end first to
> start investigating.
> Therefore I suggest to revert the change for now. Sorry if this caused any
> inconvenience.
We need a good reason for reverting (Eg: regressions in pre-existing
features). From what i read below:
> Bernhard and I we have investigated the issues reported. Issues were
> reproduced by using the newest GCC. Looks like the issues are independent
> from the target at first sight.
>
> Issues could be divided into 3 categories:
>
> 1. Issue root causes to GCC 5.x and Fortran "associated" intrinsic.
> Compiler is not reporting the âAssociated property correctly. (see test case
> 1)
> Affected tests:
> gdb.fortran/vla-ptype.exp: ptype pvla not initialized
> gdb.fortran/vla-value.exp: print undefined pvla
> gdb.fortran/vla-value.exp: print non-associated &pvla
> gdb.fortran/vla-value.exp: print undefined pvla(1,3,8)
> gdb.mi/mi-vla-fortran.exp: evaluate not associated vla
> gdb.mi/mi-vla-fortran.exp: create local variable pvla2_not_associated
> gdb.mi/mi-vla-fortran.exp: info type variable pvla2_not_associated
>
> 2. Test issues. Test take into account that array created is initialized by
> default. Initialization depends on the compiler also Fortran standard does
> not state the need for initialization.
> Affected tests:
> gdb.mi/mi-vla-fortran.exp: evaluate allocated vla
>
> 3. GCC or GDB error. Breakpoint is completely off, breakpoint on return
> line is triggered before the execution of the functions body. Deeper
> investigation should be done to define the real issue.
> Affected tests:
> gdb.cp/vla-cxx.exp
Are these regressions? Or just showing that the new feature are
not working well with the newer GCC?
I fear that, reverting central changes at this stage could
destabilize the branch, and therefore we need to be very careful
as to what we do.
--
Joel
next prev parent reply other threads:[~2016-02-09 11:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 13:47 Walfred Tedeschi
2016-02-09 11:36 ` Joel Brobecker [this message]
2016-02-09 15:14 ` Walfred Tedeschi
-- strict thread matches above, loose matches on Subject: below --
2015-07-01 12:42 [PATCH 0/2] fort_dyn_array: Enable basic Fortran dynamic " Keven Boell
2015-07-01 12:42 ` [PATCH 1/2] fort_dyn_array: add basic fortran dyn " Keven Boell
2015-07-21 18:05 ` Joel Brobecker
2015-08-05 13:41 ` Keven Boell
2015-08-05 13:47 ` Keven Boell
2015-08-05 20:23 ` Joel Brobecker
2015-08-06 11:42 ` keven.boell
2015-08-20 12:52 ` Joel Brobecker
2015-10-09 11:37 ` Keven Boell
2015-10-22 9:59 ` Joel Brobecker
2016-01-20 10:19 ` Yao Qi
2016-01-22 7:22 ` Keven Boell
2016-01-22 12:40 ` Joel Brobecker
2016-01-22 15:25 ` Yao Qi
2016-01-26 12:34 ` Joel Brobecker
[not found] ` <5613D0DC.3040908@linux.intel.com>
2015-10-22 9:59 ` Joel Brobecker
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=20160209113615.GE15342@adacore.com \
--to=brobecker@adacore.com \
--cc=bernhard.heckel@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=keven.boell@linux.intel.com \
--cc=qiyaoltc@gmail.com \
--cc=walfred.tedeschi@intel.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