Alex Bradbury via llvm-dev
2017-Nov-14 16:03 UTC
[llvm-dev] RISC-V LLVM sync-up conference calls
Dear list, At the RISC-V BoF at the LLVM Dev Meeting and the longer working session the day after, those of us working on RISC-V with LLVM decided it would be worthwhile to schedule regular sync-up calls in order to better co-ordinate ongoing work between different developers. This is primarily to sync-up, share blocking issues and so on. I understand something similar was done during the aarch64/arm64 backend upstreaming. Obviously decision making takes place through llvm/clang mailing lists with RFCs as appropriate. As everyone is spread across different timezones we're going to alternate between two time slots, switching each week. Although fully open, this is really intended for those who are actively working on RISC-V in upstream LLVM projects. If you're looking for support with issues or high level status updates it's unlikely to be useful to you. This may change as we settle in to a "rhythm" and depending on people's changing availability, but we're currently alternating between 3am UTC and 4pm UTC on Thursdays, with the next call 3am UTC on Thursday 16th. Ana Pazos will be hosting this Thursday's call, hangout/dial-in details to be confirmed. Best, Alex
Alex Bradbury via llvm-dev
2017-Nov-23 09:38 UTC
[llvm-dev] RISC-V LLVM sync-up conference calls
On 14 November 2017 at 16:03, Alex Bradbury <asb at lowrisc.org> wrote:> Dear list, > > At the RISC-V BoF at the LLVM Dev Meeting and the longer working > session the day after, those of us working on RISC-V with LLVM decided > it would be worthwhile to schedule regular sync-up calls in order to > better co-ordinate ongoing work between different developers. This is > primarily to sync-up, share blocking issues and so on. I understand > something similar was done during the aarch64/arm64 backend > upstreaming. Obviously decision making takes place through llvm/clang > mailing lists with RFCs as appropriate. As everyone is spread across > different timezones we're going to alternate between two time slots, > switching each week. Although fully open, this is really intended for > those who are actively working on RISC-V in upstream LLVM projects. If > you're looking for support with issues or high level status updates > it's unlikely to be useful to you. > > This may change as we settle in to a "rhythm" and depending on > people's changing availability, but we're currently alternating > between 3am UTC and 4pm UTC on Thursdays, with the next call 3am UTC > on Thursday 16th. Ana Pazos will be hosting this Thursday's call, > hangout/dial-in details to be confirmed.The 3am UTC time seems unpopular, so for the time being we're going to stick with 4pm UTC on a Thursday. Hangouts URL for today's discussion (4pm UTC) is https://hangouts.google.com/hangouts/_/asbradbury.org/riscvllvmdiscussion Best, Alex
Alex Bradbury via llvm-dev
2017-Nov-30 13:30 UTC
[llvm-dev] RISC-V LLVM sync-up conference calls
On 23 November 2017 at 01:38, Alex Bradbury <asb at lowrisc.org> wrote:> On 14 November 2017 at 16:03, Alex Bradbury <asb at lowrisc.org> wrote: >> Dear list, >> >> At the RISC-V BoF at the LLVM Dev Meeting and the longer working >> session the day after, those of us working on RISC-V with LLVM decided >> it would be worthwhile to schedule regular sync-up calls in order to >> better co-ordinate ongoing work between different developers. This is >> primarily to sync-up, share blocking issues and so on. I understand >> something similar was done during the aarch64/arm64 backend >> upstreaming. Obviously decision making takes place through llvm/clang >> mailing lists with RFCs as appropriate. As everyone is spread across >> different timezones we're going to alternate between two time slots, >> switching each week. Although fully open, this is really intended for >> those who are actively working on RISC-V in upstream LLVM projects. If >> you're looking for support with issues or high level status updates >> it's unlikely to be useful to you. >> >> This may change as we settle in to a "rhythm" and depending on >> people's changing availability, but we're currently alternating >> between 3am UTC and 4pm UTC on Thursdays, with the next call 3am UTC >> on Thursday 16th. Ana Pazos will be hosting this Thursday's call, >> hangout/dial-in details to be confirmed. > > The 3am UTC time seems unpopular, so for the time being we're going to > stick with 4pm UTC on a Thursday. > > Hangouts URL for today's discussion (4pm UTC) is > https://hangouts.google.com/hangouts/_/asbradbury.org/riscvllvmdiscussionSame URL, same time. (4pm UTC, about 2.5 hours from now). One of the issues we'll be discussing today is compressed instruction set, with a view to producing an RFC for wider feedback. Best, Alex
Alex Bradbury via llvm-dev
2017-Dec-07 14:31 UTC
[llvm-dev] RISC-V LLVM sync-up conference calls
On 23 November 2017 at 09:38, Alex Bradbury <asb at lowrisc.org> wrote:> On 14 November 2017 at 16:03, Alex Bradbury <asb at lowrisc.org> wrote: >> Dear list, >> >> At the RISC-V BoF at the LLVM Dev Meeting and the longer working >> session the day after, those of us working on RISC-V with LLVM decided >> it would be worthwhile to schedule regular sync-up calls in order to >> better co-ordinate ongoing work between different developers. This is >> primarily to sync-up, share blocking issues and so on. I understand >> something similar was done during the aarch64/arm64 backend >> upstreaming. Obviously decision making takes place through llvm/clang >> mailing lists with RFCs as appropriate. As everyone is spread across >> different timezones we're going to alternate between two time slots, >> switching each week. Although fully open, this is really intended for >> those who are actively working on RISC-V in upstream LLVM projects. If >> you're looking for support with issues or high level status updates >> it's unlikely to be useful to you. >> >> This may change as we settle in to a "rhythm" and depending on >> people's changing availability, but we're currently alternating >> between 3am UTC and 4pm UTC on Thursdays, with the next call 3am UTC >> on Thursday 16th. Ana Pazos will be hosting this Thursday's call, >> hangout/dial-in details to be confirmed. > > The 3am UTC time seems unpopular, so for the time being we're going to > stick with 4pm UTC on a Thursday. > > Hangouts URL for today's discussion (4pm UTC) is > https://hangouts.google.com/hangouts/_/asbradbury.org/riscvllvmdiscussionSame URL, same time (4pm UTC, 1.5 hours from now). You might be interested to know that all of my outstanding MC layer patches are now merged. If you'd like to help unblock the merge of the remaining codegen patches, I'd really appreciate a review of https://reviews.llvm.org/D39848 Best, Alex
Alex Bradbury via llvm-dev
2018-Mar-21 20:07 UTC
[llvm-dev] RISC-V LLVM sync-up conference calls
On 23 November 2017 at 09:38, Alex Bradbury <asb at lowrisc.org> wrote:> On 14 November 2017 at 16:03, Alex Bradbury <asb at lowrisc.org> wrote: >> Dear list, >> >> At the RISC-V BoF at the LLVM Dev Meeting and the longer working >> session the day after, those of us working on RISC-V with LLVM decided >> it would be worthwhile to schedule regular sync-up calls in order to >> better co-ordinate ongoing work between different developers. This is >> primarily to sync-up, share blocking issues and so on. I understand >> something similar was done during the aarch64/arm64 backend >> upstreaming. Obviously decision making takes place through llvm/clang >> mailing lists with RFCs as appropriate. As everyone is spread across >> different timezones we're going to alternate between two time slots, >> switching each week. Although fully open, this is really intended for >> those who are actively working on RISC-V in upstream LLVM projects. If >> you're looking for support with issues or high level status updates >> it's unlikely to be useful to you. >> >> This may change as we settle in to a "rhythm" and depending on >> people's changing availability, but we're currently alternating >> between 3am UTC and 4pm UTC on Thursdays, with the next call 3am UTC >> on Thursday 16th. Ana Pazos will be hosting this Thursday's call, >> hangout/dial-in details to be confirmed. > > The 3am UTC time seems unpopular, so for the time being we're going to > stick with 4pm UTC on a Thursday. > > Hangouts URL for today's discussion (4pm UTC) is > https://hangouts.google.com/hangouts/_/asbradbury.org/riscvllvmdiscussionJust to say this is still ongoing. 4pm UTC tomorrow (Thursday) at the same URL. Best, Alex