Rely from Xinmin and adding him to this thead.
IGC is open sourced. It takes SPIR-V IR and LLVM IR. We need "GCC IR to SPIR-V
translator" similar to "LLVM-IR to SPIR-V translator" we have for LLVM-IR.
How does GCC support device library?
>-Original Message-
>From: Thomas Schwinge
>Se
> On Sep 15, 2021, at 5:21 PM, Joseph Myers wrote:
>
> On Wed, 15 Sep 2021, Paul Koning via Gcc wrote:
>
>> Some questions about developer branches:
>>
>> 1. Who may create one? Who may write to them?
>> 2. Are they required to be listed in https://gcc.gnu.org/git.html ? I
>> notice it me
> On Sep 15, 2021, at 4:34 PM, Jonathan Wakely wrote:
>
> On Wed, 15 Sept 2021 at 21:12, Paul Koning via Gcc wrote:
>>
>> Some questions about developer branches:
>>
>> 1. Who may create one? Who may write to them?
>> 2. Are they required to be listed in https://gcc.gnu.org/git.html ? I
On Wed, 15 Sep 2021, Paul Koning via Gcc wrote:
> Some questions about developer branches:
>
> 1. Who may create one? Who may write to them?
> 2. Are they required to be listed in https://gcc.gnu.org/git.html ? I
> notice it mentioned a whole pile of them, most of which don't seem to
> exist.
On Wed, 15 Sept 2021 at 21:12, Paul Koning via Gcc wrote:
>
> Some questions about developer branches:
>
> 1. Who may create one? Who may write to them?
> 2. Are they required to be listed in https://gcc.gnu.org/git.html ? I notice
> it mentioned a whole pile of them, most of which don't seem t
Some questions about developer branches:
1. Who may create one? Who may write to them?
2. Are they required to be listed in https://gcc.gnu.org/git.html ? I notice
it mentioned a whole pile of them, most of which don't seem to exist.
It's a bit confusing since this seems to be a concept that i
Hi,
On Wed, 2021-09-15 16:10:50 +0200, Mark Wielaard wrote:
[UTF-8 email address containing a 'ł']
> The issue is the gravatar support, which calls md5_hex($email).
> For now I disabled gravatar support on sourceware.org/gcc.gnu.org in
> /etc/gitweb.conf
I am not a Perl guy, but it seems this wo
On 9/14/21 3:43 AM, Basile Starynkevitch wrote:
On 9/14/21 11:32 AM, Martin Liška wrote:
On 9/10/21 15:05, Basile Starynkevitch wrote:
Hello all,
In the Bismon static source code analyzer on
https://github.com/bstarynk/bismon/ commit ad8b6270691e
(funded by http://decoder-project.eu/ )
Hi Jonathan!
On Wed, 2021-09-15 14:43:45 +0100, Jonathan Wakely
wrote:
> On Wed, 15 Sept 2021 at 14:37, Jan-Benedict Glaw wrote:
[UTF-8 in committer's email addresses]
> > So I broke it. Any way to make sure something like this doesn't
> > occur again?
>
> We could add a check to the git hoo
Hi,
On Wed, 2021-09-15 at 14:43 +0100, Jonathan Wakely via Gcc wrote:
> On Wed, 15 Sept 2021 at 14:37, Jan-Benedict Glaw
> wrote:
> > On Wed, 2021-09-15 09:21:04 -0400, David Malcolm via Gcc <
> > gcc@gcc.gnu.org> wrote:
> > > It appears to be due to the "ł" character in the email address of
> >
Hi Feng,
On Tue, Sep 14 2021, Feng Xue OS via Gcc wrote:
> Ping again.
>
I have read your email but do not have much to comment. I think that
you have identified all the potential issues yourself. IIUC, I am
afraid that they will mean that at least the "Typeinfo symbol resolution
by linker-plug
On Wed, 15 Sept 2021 at 14:37, Jan-Benedict Glaw wrote:
>
> Hi David, Jonathan and all others,
>
> On Wed, 2021-09-15 09:21:04 -0400, David Malcolm via Gcc
> wrote:
> > On Mon, 2021-09-13 at 14:03 +0100, Jonathan Wakely via Gcc wrote:
> > > On Mon, 13 Sept 2021 at 14:01, Jonathan Wakely
> > >
Hi David, Jonathan and all others,
On Wed, 2021-09-15 09:21:04 -0400, David Malcolm via Gcc
wrote:
> On Mon, 2021-09-13 at 14:03 +0100, Jonathan Wakely via Gcc wrote:
> > On Mon, 13 Sept 2021 at 14:01, Jonathan Wakely
> > wrote:
> > > On Mon, 13 Sept 2021 at 13:53, Thomas Koenig via Gcc
> >
On Mon, 2021-09-13 at 14:03 +0100, Jonathan Wakely via Gcc wrote:
> On Mon, 13 Sept 2021 at 14:01, Jonathan Wakely
> wrote:
> >
> > On Mon, 13 Sept 2021 at 13:53, Thomas Koenig via Gcc <
> > gcc@gcc.gnu.org> wrote:
> > >
> > > Hi,
> > >
> > > I just got an error when accessing the gcc git pages
On Mon, 13 Sept 2021 at 14:03, Jonathan Wakely wrote:
>
> On Mon, 13 Sept 2021 at 14:01, Jonathan Wakely wrote:
> >
> > On Mon, 13 Sept 2021 at 13:53, Thomas Koenig via Gcc
> > wrote:
> > >
> > > Hi,
> > >
> > > I just got an error when accessing the gcc git pages at
> > > https://gcc.gnu.org/g
Hi!
On 2021-09-15T02:00:33+, "Liu, Hongtao via Gcc" wrote:
> I got some feedback from my colleague
Thanks for reaching out to them.
> -
> What we need from GCC
>
> 1. generate SPIR-V
> 2. offload bundler to create FAT object
> --
>
> If the answer is yes for both
On Wed, 15 Sept 2021 at 10:02, Fredrik Hederstierna wrote:
>
> I have a question about array index bounds check that I do not fully
> understand.
This question belongs on the gcc-help mailing list instead.
> Compiling the code below, I get warnings for out-of-bounds in one case, but
> not the
On Wed, Sep 15, 2021 at 11:19:29AM +0200, Richard Biener wrote:
> On Wed, Sep 15, 2021 at 4:02 AM Liu, Hongtao via Gcc wrote:
> >
> > I got some feedback from my colleague
> >
> > -
> > What we need from GCC
> >
> > 1. generate SPIR-V
>
> But is SPIR-V powerful enough here, if wik
On Wed, Sep 15, 2021 at 4:02 AM Liu, Hongtao via Gcc wrote:
>
> I got some feedback from my colleague
>
> -
> What we need from GCC
>
> 1. generate SPIR-V
But is SPIR-V powerful enough here, if wikipedia is right and it is
close to GLSL
then it likely has not the ability to perfor
I have a question about array index bounds check that I do not fully understand.
Compiling the code below, I get warnings for out-of-bounds in one case, but not
the other,
also printf output gets different, but should be same?
Maybe someone can explain what is going on, and if observed behavior is
On 14/09/2021 20:48, Rafał Pietrak wrote:
W dniu 13.09.2021 o 13:41, David Brown pisze:
On 13/09/2021 11:51, Rafał Pietrak via Gcc wrote:
Hi,
Thenk you for very prompt reply.
(I'm not sure how much this is a "gcc development list" matter, rather
than perhaps a "gcc help list" or perhaps
21 matches
Mail list logo
