On Mon, 2020-02-24 at 12:36 +0100, Petr Tesarik wrote:
> On Mon, 24 Feb 2020 11:14:44 +
> Jozef Lawrynowicz wrote:
>
> > On Mon, 24 Feb 2020 12:05:28 +0100
> > Petr Tesarik wrote:
> >
> > > Hi all,
> > >
> > > I'm looking into reviving the efforts to port gcc to VideoCore IV [1].
> > > One
You keep talking about a broken link without telling us where it is.
But I don't think we're interested anyway, that's why nobody has replied.
On Mon, 24 Feb 2020 at 12:24, Richard @ Quality Nonsense PR Team
wrote:
>
> Dear GCC Team,
>
> Just checking in one last time to make sure we don't get
On Mon, 24 Feb 2020 15:03:21 +0300 (MSK)
Alexander Monakov wrote:
> On Mon, 24 Feb 2020, Andreas Schwab wrote:
>
> > On Feb 24 2020, Petr Tesarik wrote:
> >
> > > On Mon, 24 Feb 2020 12:29:40 +0100
> > > Andreas Schwab wrote:
> > >
> > >> On Feb 24 2020, Petr Tesarik wrote:
> > >>
> > >
On Mon, 24 Feb 2020 15:03:21 +0300 (MSK)
Alexander Monakov wrote:
> On Mon, 24 Feb 2020, Andreas Schwab wrote:
>
> > On Feb 24 2020, Petr Tesarik wrote:
> >
> > > On Mon, 24 Feb 2020 12:29:40 +0100
> > > Andreas Schwab wrote:
> > >
> > >> On Feb 24 2020, Petr Tesarik wrote:
> > >>
> > >
Dear GCC Team,
Just checking in one last time to make sure we don't get overlooked in your
inbox.
Is there anything stopping you from recommending our long read about Digital
Equipment Corporation to your users instead of the broken DEC link, out of
interest?
I'm always interested in actiona
On Mon, 24 Feb 2020, Andreas Schwab wrote:
> On Feb 24 2020, Petr Tesarik wrote:
>
> > On Mon, 24 Feb 2020 12:29:40 +0100
> > Andreas Schwab wrote:
> >
> >> On Feb 24 2020, Petr Tesarik wrote:
> >>
> >> > This works great ... until there's some inline asm() statement, for
> >> > which gcc canno
On Feb 24 2020, Petr Tesarik wrote:
> On Mon, 24 Feb 2020 12:29:40 +0100
> Andreas Schwab wrote:
>
>> On Feb 24 2020, Petr Tesarik wrote:
>>
>> > This works great ... until there's some inline asm() statement, for
>> > which gcc cannot keep track of the length attribute, so it is probably
>> > t
On 24/02/2020 11:05, Petr Tesarik wrote:
Hi all,
I'm looking into reviving the efforts to port gcc to VideoCore IV [1].
One issue I've run into is the need to find out target branch distance
at compile time. I looked around, and it's not the first one
architecture with such requirement, but AFAI
On Mon, 24 Feb 2020 12:29:40 +0100
Andreas Schwab wrote:
> On Feb 24 2020, Petr Tesarik wrote:
>
> > This works great ... until there's some inline asm() statement, for
> > which gcc cannot keep track of the length attribute, so it is probably
> > taken as zero.
>
> GCC computes it by countin
On Mon, 24 Feb 2020 11:14:44 +
Jozef Lawrynowicz wrote:
> On Mon, 24 Feb 2020 12:05:28 +0100
> Petr Tesarik wrote:
>
> > Hi all,
> >
> > I'm looking into reviving the efforts to port gcc to VideoCore IV [1].
> > One issue I've run into is the need to find out target branch distance
> > at
On Feb 24 2020, Petr Tesarik wrote:
> This works great ... until there's some inline asm() statement, for
> which gcc cannot keep track of the length attribute, so it is probably
> taken as zero.
GCC computes it by counting the number of asm insns. You can use
ADJUST_INSN_LENGTH to adjust this a
On Mon, 24 Feb 2020 12:05:28 +0100
Petr Tesarik wrote:
> Hi all,
>
> I'm looking into reviving the efforts to port gcc to VideoCore IV [1].
> One issue I've run into is the need to find out target branch distance
> at compile time. I looked around, and it's not the first one
> architecture with
Hi all,
I'm looking into reviving the efforts to port gcc to VideoCore IV [1].
One issue I've run into is the need to find out target branch distance
at compile time. I looked around, and it's not the first one
architecture with such requirement, but AFAICS it has never been solved
properly.
For
13 matches
Mail list logo
