On 09/01/2016 09:04 AM, Martin Sebor wrote:
Understood. I think a write-only attribute or type qualifier would
make sense. Until/unless it's implemented I would recommend to work
around its absence by hiding access to the registers behind a read-
only and write-only functional API.
As you note
On Wed, Sep 7, 2016 at 9:21 AM, augustine.sterl...@gmail.com
wrote:
> Hope this helps, and I'm happy to answer more questions.
Also, one technique commonly used by people who ship software for
Xtensa is to write it such that it could compile for any variant at
all. This requires care, but is quit
On Tue, Sep 6, 2016 at 11:55 PM, Thomas Schwinge
wrote:
> Hi!
>
> Neither do I really know anything about Xtensa, nor do I have a lot of
> experience in these parts of GCC back ends, but:
There is a lot of background to know here. Unfortunately, I have no
familiarity with making debian packages,
On Wed, Sep 7, 2016 at 1:52 PM, Thomas Schwinge wrote:
> Hi!
>
> I trimmed the CC list -- I'm looking for advice about debugging a lto1
> ICE.
>
> On Fri, 19 Aug 2016 11:05:59 +, Joseph Myers
> wrote:
>> On Fri, 19 Aug 2016, Richard Biener wrote:
>> > Can you quickly verify if LTO works with
Hi!
I trimmed the CC list -- I'm looking for advice about debugging a lto1
ICE.
On Fri, 19 Aug 2016 11:05:59 +, Joseph Myers
wrote:
> On Fri, 19 Aug 2016, Richard Biener wrote:
> > Can you quickly verify if LTO works with the new types? I don't see
> > anything
> > that would prevent it b
Hello,
On Tue, Sep 6, 2016 at 11:42 AM, Oleksij Rempel wrote:
> i'm one of ath9k-htc-firmware developers. Currently i'm looking for the
> way to provide this firmware as opensource/free package for debian. Main
> problem seems to be the need to patch gcc xtensa-config.h to make it
> suitable for
