Hello All,
I looked at FINAL_PRESCAN_INSN, and as Ian mentioned, I do not
have any CFG info or the basic block pointers. I really would like to
reporoduce that information at that stage. I looked at passes.c and the
cfgbuild.c, and if I do thefollowing:
ind_basic_blocks(get_insns());
Compu
Sean D'Epagnier wrote:
I am working toward efficient support of some of the sfixed point
types on avr architecture.
I started out by writing an assembly library to handle all of the
conversions to and from various fixed point, integer, and floating
point types. In many cases the functions are o
Steve Kargl wrote:
I have no idea what you and Toon are discussing. These
options are not used in the gfortran frontend and have never
been used. Looking at the g77 manual suggests that
-fargument-noalias-global is a holdover from g77, and as such
it should be removed.
It is the Fortran pro
On Sat, 3 Jan 2009, Steve Kargl wrote:
> On Sat, Jan 03, 2009 at 08:11:14PM +0100, Richard Guenther wrote:
> > On Sat, 3 Jan 2009, Toon Moene wrote:
> >
> > > [ Happy New Year first of all - hope we don't have too many more of them
> > > ... Hey, you can recognize a Jimi Hendrix fan, don't you
On Sat, Jan 03, 2009 at 08:11:14PM +0100, Richard Guenther wrote:
> On Sat, 3 Jan 2009, Toon Moene wrote:
>
> > [ Happy New Year first of all - hope we don't have too many more of them
> > ... Hey, you can recognize a Jimi Hendrix fan, don't you ]
>
> ;)
>
> > Richard Guenther wrote:
> >
> >
Richard Guenther wrote:
I btw installed that (wrong?) patch based on the answers I got.
My apologies - see above.
At least the wrong patch makes foo see that the array data does not alias.
Maybe we need to fix the specification?
If we internalize those two optimization flags to the Fortr
On Sat, 3 Jan 2009, Toon Moene wrote:
> Richard Guenther wrote:
>
> > On Sat, 3 Jan 2009, Toon Moene wrote:
>
> > > The pointers used by the Fortran Front End to implement Fortran's argument
> > > association *cannot* point to anything else than the storage of those
> > > arguments, because they
Richard Guenther wrote:
On Sat, 3 Jan 2009, Toon Moene wrote:
The pointers used by the Fortran Front End to implement Fortran's argument
association *cannot* point to anything else than the storage of those
arguments, because they (those pointers) are generated by the compiler and
cannot poin
Toon Moene wrote:
Richard Guenther wrote:
consider
void bar()
{
int i;
p = &i;
foo (&i);
}
does that call to foo invoke undefined behavior if built with
-fargument-noalias-global?
It shouldn't, as 'int i' isn't global.
Ugh, on second thoughts, this isn't possible in Fortran, so I
On Sat, 3 Jan 2009, Toon Moene wrote:
> [ Happy New Year first of all - hope we don't have too many more of them
> ... Hey, you can recognize a Jimi Hendrix fan, don't you ]
;)
> Richard Guenther wrote:
>
> > Actually I have two questions. First, what is the difference between
> > -fargument
[ Happy New Year first of all - hope we don't have too many more of them
... Hey, you can recognize a Jimi Hendrix fan, don't you ]
Richard Guenther wrote:
Actually I have two questions. First, what is the difference between
-fargument-noalias-global and -fargument-noalias-anything (please
p
Actually I have two questions. First, what is the difference between
-fargument-noalias-global and -fargument-noalias-anything (please
provide an example, not cite documentation ;))
Second question. Does "global memory" include memory that escaped?
Thus, with -fargument-noalias-global:
int *p;
"Richard Guenther" writes:
> On Fri, Jan 2, 2009 at 12:36 PM, Richard Sandiford
> wrote:
>> Hi,
>>
>> Sorry in advance if this going over old ground. And if not, sorry
>> for the somewhat negative message ;), but ... I think the current
>> documentation and/or behaviour of the "optimize" attrib
13 matches
Mail list logo
