llvm dev - Mar 2017 - [EuroLLVM] Hacker's Lab - Topics and Volunteers needed!

The hacker's lab will be organized similar to the one at the US 2016
meeting [0]. That means 1.5 hour sessions and theme tables in the
different rooms. Each table (~10) will have a sign on it to represent a
sub-project or area of LLVM. This will help newcomers and even active
developers congregate together on specific topics.

In addition to labeling tables, we are asking for volunteers to
represent a sub-project or topic related to the meeting. These
volunteers should be knowledgeable about the sub-project/topic and able
to answer some basic questions or point people to the right developer to
talk to. If volunteers want to go a step further, they could prepare a
list of bugs that groups could work on during the Hackers Lab. This is
very open ended in what the leader of the table can do, but the main
goal is to provide a space for developers' to meet and find each other
who are interested in a specific topic or sub-project.

Possible topics include, but are not limited to:

  LLVM
  Backends, Code Generation, Register Allocation, Machine Code Layer, ISel
  LLDB, Debug Info, DWARF
  LTO
  Polly
  MCJIT
  Mid-level optimizations, pass manager, loop optimizations, etc
  TableGen
  Sanitizers
  Windows support
  Exception handling
  lld

  Clang, Libs, & Frontend tools
  Clang - parsing, LLVM IR generation, etc
  Static Analyzer
  OpenCL
  Clang Tools - clang tidy, clang rename
  parallel-libs
  Open MP
  libC++
  llgo


Please let us know ASAP if you are interested! In the rare event there
are too many volunteers, we may combine topics at tables.

--
  The EuroLLVM'17 organization team

PS. Heavily based on Tanya's email (see [0]).

[0] http://lists.llvm.org/pipermail/llvm-dev/2016-October/106394.html

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: Digital signature
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20170308/2f7f6607/attachment.sig>

On 8 March 2017 at 16:10, Johannes Doerfert via llvm-devmeeting
<llvm-devmeeting at lists.llvm.org> wrote:
>   Backends,
It'd be good to have one table for each (combined) back-end, at least
one for Intel (32/64) and ARM (32/64).

I volunteer to stay at the ARM table.

>   Polly
>   parallel-libs
>   Open MP
I also want to talk about HPC-specific optimisations in LLVM (FP,
loop, vectoriser), which would intersect with those three topics.

We could have those tables in sequence or next to each other?

cheers,
--renato

On Mon, Mar 13, 2017, at 01:46 PM, Renato Golin via llvm-devmeeting
wrote:
> On 8 March 2017 at 16:10, Johannes Doerfert via llvm-devmeeting
> <llvm-devmeeting at lists.llvm.org> wrote:
> >   Backends,
> 
> It'd be good to have one table for each (combined) back-end, at least
> one for Intel (32/64) and ARM (32/64).
> 
> I volunteer to stay at the ARM table.
> 
> 
> >   Polly
> >   parallel-libs
> >   Open MP
> 
> I also want to talk about HPC-specific optimisations in LLVM (FP,
> loop, vectoriser), which would intersect with those three topics.
> 
> We could have those tables in sequence or next to each other?
Hi Renato, hi Johannes,

would be glad to have a table around loop optimization or LLVM in HPC.

Best,
Tobias
> 
> cheers,
> --renato
> _______________________________________________
> llvm-devmeeting mailing list
> llvm-devmeeting at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-devmeeting

>  MCJIT
How about ORC JIT table? Or just LLVM + JIT in general? I’m not proficient
enough to “lead” the table, but I would be very interested to join discussions.
> On 8 Mar 2017, at 17:10, Johannes Doerfert via llvm-devmeeting
<llvm-devmeeting at lists.llvm.org> wrote:
> 
> The hacker's lab will be organized similar to the one at the US 2016
> meeting [0]. That means 1.5 hour sessions and theme tables in the
> different rooms. Each table (~10) will have a sign on it to represent a
> sub-project or area of LLVM. This will help newcomers and even active
> developers congregate together on specific topics.
> 
> In addition to labeling tables, we are asking for volunteers to
> represent a sub-project or topic related to the meeting. These
> volunteers should be knowledgeable about the sub-project/topic and able
> to answer some basic questions or point people to the right developer to
> talk to. If volunteers want to go a step further, they could prepare a
> list of bugs that groups could work on during the Hackers Lab. This is
> very open ended in what the leader of the table can do, but the main
> goal is to provide a space for developers' to meet and find each other
> who are interested in a specific topic or sub-project.
> 
> Possible topics include, but are not limited to:
> 
>  LLVM
>  Backends, Code Generation, Register Allocation, Machine Code Layer, ISel
>  LLDB, Debug Info, DWARF
>  LTO
>  Polly
>  MCJIT
>  Mid-level optimizations, pass manager, loop optimizations, etc
>  TableGen
>  Sanitizers
>  Windows support
>  Exception handling
>  lld
> 
>  Clang, Libs, & Frontend tools
>  Clang - parsing, LLVM IR generation, etc
>  Static Analyzer
>  OpenCL
>  Clang Tools - clang tidy, clang rename
>  parallel-libs
>  Open MP
>  libC++
>  llgo
> 
> 
> Please let us know ASAP if you are interested! In the rare event there
> are too many volunteers, we may combine topics at tables.
> 
> --
>  The EuroLLVM'17 organization team
> 
> PS. Heavily based on Tanya's email (see [0]).
> 
> [0] http://lists.llvm.org/pipermail/llvm-dev/2016-October/106394.html
> 
> _______________________________________________
> llvm-devmeeting mailing list
> llvm-devmeeting at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-devmeeting
-- 
AlexDenisov
Software Engineer, https://lowlevelbits.org

I can volunteer to be at the OpenCL table.

Might be worthwhile to have it be expanded to GPUs in general, so it
covers a wider range of topics.

On 8 March 2017 at 16:10, Johannes Doerfert via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> The hacker's lab will be organized similar to the one at the US 2016
> meeting [0]. That means 1.5 hour sessions and theme tables in the
> different rooms. Each table (~10) will have a sign on it to represent a
> sub-project or area of LLVM. This will help newcomers and even active
> developers congregate together on specific topics.
>
> In addition to labeling tables, we are asking for volunteers to
> represent a sub-project or topic related to the meeting. These
> volunteers should be knowledgeable about the sub-project/topic and able
> to answer some basic questions or point people to the right developer to
> talk to. If volunteers want to go a step further, they could prepare a
> list of bugs that groups could work on during the Hackers Lab. This is
> very open ended in what the leader of the table can do, but the main
> goal is to provide a space for developers' to meet and find each other
> who are interested in a specific topic or sub-project.
>
> Possible topics include, but are not limited to:
>
>   LLVM
>   Backends, Code Generation, Register Allocation, Machine Code Layer, ISel
>   LLDB, Debug Info, DWARF
>   LTO
>   Polly
>   MCJIT
>   Mid-level optimizations, pass manager, loop optimizations, etc
>   TableGen
>   Sanitizers
>   Windows support
>   Exception handling
>   lld
>
>   Clang, Libs, & Frontend tools
>   Clang - parsing, LLVM IR generation, etc
>   Static Analyzer
>   OpenCL
>   Clang Tools - clang tidy, clang rename
>   parallel-libs
>   Open MP
>   libC++
>   llgo
>
>
> Please let us know ASAP if you are interested! In the rare event there
> are too many volunteers, we may combine topics at tables.
>
> --
>   The EuroLLVM'17 organization team
>
> PS. Heavily based on Tanya's email (see [0]).
>
> [0] http://lists.llvm.org/pipermail/llvm-dev/2016-October/106394.html
>
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>

I can volunteer to be at the OpenCL table.

Might be worthwhile to have it be expanded to GPUs in general, so it
covers a wider range of topics.

On 8 March 2017 at 16:10, Johannes Doerfert via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> The hacker's lab will be organized similar to the one at the US 2016
> meeting [0]. That means 1.5 hour sessions and theme tables in the
> different rooms. Each table (~10) will have a sign on it to represent a
> sub-project or area of LLVM. This will help newcomers and even active
> developers congregate together on specific topics.
>
> In addition to labeling tables, we are asking for volunteers to
> represent a sub-project or topic related to the meeting. These
> volunteers should be knowledgeable about the sub-project/topic and able
> to answer some basic questions or point people to the right developer to
> talk to. If volunteers want to go a step further, they could prepare a
> list of bugs that groups could work on during the Hackers Lab. This is
> very open ended in what the leader of the table can do, but the main
> goal is to provide a space for developers' to meet and find each other
> who are interested in a specific topic or sub-project.
>
> Possible topics include, but are not limited to:
>
>   LLVM
>   Backends, Code Generation, Register Allocation, Machine Code Layer, ISel
>   LLDB, Debug Info, DWARF
>   LTO
>   Polly
>   MCJIT
>   Mid-level optimizations, pass manager, loop optimizations, etc
>   TableGen
>   Sanitizers
>   Windows support
>   Exception handling
>   lld
>
>   Clang, Libs, & Frontend tools
>   Clang - parsing, LLVM IR generation, etc
>   Static Analyzer
>   OpenCL
>   Clang Tools - clang tidy, clang rename
>   parallel-libs
>   Open MP
>   libC++
>   llgo
>
>
> Please let us know ASAP if you are interested! In the rare event there
> are too many volunteers, we may combine topics at tables.
>
> --
>   The EuroLLVM'17 organization team
>
> PS. Heavily based on Tanya's email (see [0]).
>
> [0] http://lists.llvm.org/pipermail/llvm-dev/2016-October/106394.html
>
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>

I'll be happy to discuss anything related to LNT and test-suite.

> On 8 Mar 2017, at 17:10, Johannes Doerfert via llvm-dev <llvm-dev at
lists.llvm.org> wrote:
> 
> The hacker's lab will be organized similar to the one at the US 2016
> meeting [0]. That means 1.5 hour sessions and theme tables in the
> different rooms. Each table (~10) will have a sign on it to represent a
> sub-project or area of LLVM. This will help newcomers and even active
> developers congregate together on specific topics.
> 
> In addition to labeling tables, we are asking for volunteers to
> represent a sub-project or topic related to the meeting. These
> volunteers should be knowledgeable about the sub-project/topic and able
> to answer some basic questions or point people to the right developer to
> talk to. If volunteers want to go a step further, they could prepare a
> list of bugs that groups could work on during the Hackers Lab. This is
> very open ended in what the leader of the table can do, but the main
> goal is to provide a space for developers' to meet and find each other
> who are interested in a specific topic or sub-project.
> 
> Possible topics include, but are not limited to:
> 
>  LLVM
>  Backends, Code Generation, Register Allocation, Machine Code Layer, ISel
>  LLDB, Debug Info, DWARF
>  LTO
>  Polly
>  MCJIT
>  Mid-level optimizations, pass manager, loop optimizations, etc
>  TableGen
>  Sanitizers
>  Windows support
>  Exception handling
>  lld
> 
>  Clang, Libs, & Frontend tools
>  Clang - parsing, LLVM IR generation, etc
>  Static Analyzer
>  OpenCL
>  Clang Tools - clang tidy, clang rename
>  parallel-libs
>  Open MP
>  libC++
>  llgo
> 
> 
> Please let us know ASAP if you are interested! In the rare event there
> are too many volunteers, we may combine topics at tables.
> 
> --
>  The EuroLLVM'17 organization team
> 
> PS. Heavily based on Tanya's email (see [0]).
> 
> [0] http://lists.llvm.org/pipermail/llvm-dev/2016-October/106394.html
> 
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

I'm happy to help with any of:

On Wed, Mar 8, 2017 at 8:13 AM Johannes Doerfert via llvm-devmeeting <
llvm-devmeeting at lists.llvm.org> wrote:
>   LLVM
>   LTO
>   Mid-level optimizations, pass manager, loop optimizations, etc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20170320/f67a7d1b/attachment.html>

Noted, thanks!

On 03/20, Kristof Beyls wrote:
> I'll be happy to discuss anything related to LNT and test-suite.
> 
> 
> > On 8 Mar 2017, at 17:10, Johannes Doerfert via llvm-dev <llvm-dev
at lists.llvm.org> wrote:
> > 
> > The hacker's lab will be organized similar to the one at the US
2016
> > meeting [0]. That means 1.5 hour sessions and theme tables in the
> > different rooms. Each table (~10) will have a sign on it to represent
a
> > sub-project or area of LLVM. This will help newcomers and even active
> > developers congregate together on specific topics.
> > 
> > In addition to labeling tables, we are asking for volunteers to
> > represent a sub-project or topic related to the meeting. These
> > volunteers should be knowledgeable about the sub-project/topic and
able
> > to answer some basic questions or point people to the right developer
to
> > talk to. If volunteers want to go a step further, they could prepare a
> > list of bugs that groups could work on during the Hackers Lab. This is
> > very open ended in what the leader of the table can do, but the main
> > goal is to provide a space for developers' to meet and find each
other
> > who are interested in a specific topic or sub-project.
> > 
> > Possible topics include, but are not limited to:
> > 
> >  LLVM
> >  Backends, Code Generation, Register Allocation, Machine Code Layer,
ISel
> >  LLDB, Debug Info, DWARF
> >  LTO
> >  Polly
> >  MCJIT
> >  Mid-level optimizations, pass manager, loop optimizations, etc
> >  TableGen
> >  Sanitizers
> >  Windows support
> >  Exception handling
> >  lld
> > 
> >  Clang, Libs, & Frontend tools
> >  Clang - parsing, LLVM IR generation, etc
> >  Static Analyzer
> >  OpenCL
> >  Clang Tools - clang tidy, clang rename
> >  parallel-libs
> >  Open MP
> >  libC++
> >  llgo
> > 
> > 
> > Please let us know ASAP if you are interested! In the rare event there
> > are too many volunteers, we may combine topics at tables.
> > 
> > --
> >  The EuroLLVM'17 organization team
> > 
> > PS. Heavily based on Tanya's email (see [0]).
> > 
> > [0] http://lists.llvm.org/pipermail/llvm-dev/2016-October/106394.html
> > 
> > _______________________________________________
> > LLVM Developers mailing list
> > llvm-dev at lists.llvm.org
> > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
> 
-- 

Johannes Doerfert
Researcher / PhD Student

Compiler Design Lab (Prof. Hack)
Saarland Informatics Campus, Germany
Building E1.3, Room 4.31

Tel. +49 (0)681 302-57521 : doerfert at cs.uni-saarland.de
Fax. +49 (0)681 302-3065  : http://www.cdl.uni-saarland.de/people/doerfert
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: Digital signature
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20170320/af0bc2f2/attachment.sig>

Noted, thanks!

On 03/20, Chandler Carruth wrote:
> I'm happy to help with any of:
> 
> On Wed, Mar 8, 2017 at 8:13 AM Johannes Doerfert via llvm-devmeeting <
> llvm-devmeeting at lists.llvm.org> wrote:
> 
> >   LLVM
> >   LTO
> >   Mid-level optimizations, pass manager, loop optimizations, etc
> >
-- 

Johannes Doerfert
Researcher / PhD Student

Compiler Design Lab (Prof. Hack)
Saarland Informatics Campus, Germany
Building E1.3, Room 4.31

Tel. +49 (0)681 302-57521 : doerfert at cs.uni-saarland.de
Fax. +49 (0)681 302-3065  : http://www.cdl.uni-saarland.de/people/doerfert
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: Digital signature
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20170320/3bec6cf5/attachment.sig>

Hello,

If there is a table on Exception handling, Can I have a slot in the 
agenda to discuss a proposal to clarify and adapt the attributes used to 
handle the exception/unwind flags from clang ?. That can be at the ARM 
table as well.

thanks,

Christian

Le 03/08/2017 à 05:10 PM, Johannes Doerfert via llvm-dev a écrit
:
> The hacker's lab will be organized similar to the one at the US 2016
> meeting [0]. That means 1.5 hour sessions and theme tables in the
> different rooms. Each table (~10) will have a sign on it to represent a
> sub-project or area of LLVM. This will help newcomers and even active
> developers congregate together on specific topics.
>
> In addition to labeling tables, we are asking for volunteers to
> represent a sub-project or topic related to the meeting. These
> volunteers should be knowledgeable about the sub-project/topic and able
> to answer some basic questions or point people to the right developer to
> talk to. If volunteers want to go a step further, they could prepare a
> list of bugs that groups could work on during the Hackers Lab. This is
> very open ended in what the leader of the table can do, but the main
> goal is to provide a space for developers' to meet and find each other
> who are interested in a specific topic or sub-project.
>
> Possible topics include, but are not limited to:
>
>    LLVM
>    Backends, Code Generation, Register Allocation, Machine Code Layer, ISel
>    LLDB, Debug Info, DWARF
>    LTO
>    Polly
>    MCJIT
>    Mid-level optimizations, pass manager, loop optimizations, etc
>    TableGen
>    Sanitizers
>    Windows support
>    Exception handling
>    lld
>
>    Clang, Libs, & Frontend tools
>    Clang - parsing, LLVM IR generation, etc
>    Static Analyzer
>    OpenCL
>    Clang Tools - clang tidy, clang rename
>    parallel-libs
>    Open MP
>    libC++
>    llgo
>
>
> Please let us know ASAP if you are interested! In the rare event there
> are too many volunteers, we may combine topics at tables.
>
> --
>    The EuroLLVM'17 organization team
>
> PS. Heavily based on Tanya's email (see [0]).
>
> [0] http://lists.llvm.org/pipermail/llvm-dev/2016-October/106394.html
>
>
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20170324/5584ba54/attachment-0001.html>

Hi Christian,

We put your name down for an exception handling table at the same time &
room as the ARM (32/64) table [Renato]. I hope this is OK with you.

Thanks!

--
  Johannes


On 03/24, Christian Bruel wrote:
> Hello,
> 
> If there is a table on Exception handling, Can I have a slot in the agenda
> to discuss a proposal to clarify and adapt the attributes used to handle
the
> exception/unwind flags from clang ?. That can be at the ARM table as well.
> 
> thanks,
> 
> Christian
> 
> Le 03/08/2017 à 05:10 PM, Johannes Doerfert via llvm-dev a écrit :
> >The hacker's lab will be organized similar to the one at the US
2016
> >meeting [0]. That means 1.5 hour sessions and theme tables in the
> >different rooms. Each table (~10) will have a sign on it to represent a
> >sub-project or area of LLVM. This will help newcomers and even active
> >developers congregate together on specific topics.
> >
> >In addition to labeling tables, we are asking for volunteers to
> >represent a sub-project or topic related to the meeting. These
> >volunteers should be knowledgeable about the sub-project/topic and able
> >to answer some basic questions or point people to the right developer
to
> >talk to. If volunteers want to go a step further, they could prepare a
> >list of bugs that groups could work on during the Hackers Lab. This is
> >very open ended in what the leader of the table can do, but the main
> >goal is to provide a space for developers' to meet and find each
other
> >who are interested in a specific topic or sub-project.
> >
> >Possible topics include, but are not limited to:
> >
> >   LLVM
> >   Backends, Code Generation, Register Allocation, Machine Code Layer,
ISel
> >   LLDB, Debug Info, DWARF
> >   LTO
> >   Polly
> >   MCJIT
> >   Mid-level optimizations, pass manager, loop optimizations, etc
> >   TableGen
> >   Sanitizers
> >   Windows support
> >   Exception handling
> >   lld
> >
> >   Clang, Libs, & Frontend tools
> >   Clang - parsing, LLVM IR generation, etc
> >   Static Analyzer
> >   OpenCL
> >   Clang Tools - clang tidy, clang rename
> >   parallel-libs
> >   Open MP
> >   libC++
> >   llgo
> >
> >
> >Please let us know ASAP if you are interested! In the rare event there
> >are too many volunteers, we may combine topics at tables.
> >
> >--
> >   The EuroLLVM'17 organization team
> >
> >PS. Heavily based on Tanya's email (see [0]).
> >
> >[0] http://lists.llvm.org/pipermail/llvm-dev/2016-October/106394.html
> >
> >
> >
> >_______________________________________________
> >LLVM Developers mailing list
> >llvm-dev at lists.llvm.org
> >http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
> 
-- 

Johannes Doerfert
Researcher / PhD Student

Compiler Design Lab (Prof. Hack)
Saarland Informatics Campus, Germany
Building E1.3, Room 4.31

Tel. +49 (0)681 302-57521 : doerfert at cs.uni-saarland.de
Fax. +49 (0)681 302-3065  : http://www.cdl.uni-saarland.de/people/doerfert
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: Digital signature
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20170324/cb74d085/attachment.sig>