Hanke Zhang via Gcc writes:
> Hi Filip,
>
> Thanks for your reply. But I'm not so familiar with VIM actually. Thus
> when I try the options listed there, nothing happened. (VSCODE is the
> IDE I'm using for development.)
>
> And I notice that there is a `vimrc` in the `contrib` directory, I
> tri
Bootstrapping the following configuration (with LRA enabled) looks good
for ia64, too:
```
CFLAGS="-O2 -fPIC" \
CXXFLAGS="-O2 -fPIC" \
../configure --prefix=/usr \
--enable-obsolete \
--libdir=/usr/lib \
--mandir=/usr/man \
--infodir=/usr/info \
--enable-shared \
--enable-bootstrap \
--enable-lan
On 4/22/24 9:24 PM, Tom Tromey wrote:
Jason> Someone mentioned earlier that gerrit was previously tried
Jason> unsuccessfully.
We tried it and gdb and then abandoned it. We tried to integrate it
into the traditional gdb development style, having it send email to
gdb-patches. I found these s
On Wed, 1 May 2024 at 20:19, Jeff Law via Gcc wrote:
>
>
>
> On 4/22/24 9:24 PM, Tom Tromey wrote:
> > Jason> Someone mentioned earlier that gerrit was previously tried
> > Jason> unsuccessfully.
> >
> > We tried it and gdb and then abandoned it. We tried to integrate it
> > into the traditional
On 5/1/24 12:15, Jeff Law wrote:
On 4/22/24 9:24 PM, Tom Tromey wrote:
Jason> Someone mentioned earlier that gerrit was previously tried
Jason> unsuccessfully.
We tried it and gdb and then abandoned it. We tried to integrate it
into the traditional gdb development style, having it send email
Hi Jonathan,
On Wed, May 01, 2024 at 08:38:26PM +0100, Jonathan Wakely wrote:
> On Wed, 1 May 2024 at 20:19, Jeff Law via Gcc wrote:
> > We're currently using patchwork to track patches tagged with RISC-V. We
> > don't do much review with patchwork. In that model patchwork ultimately
> > just a
Mark> See also https://sourceware.org/bugzilla/show_bug.cgi?id=30997
Mark> We really should automate this. There are several people running
Mark> scripts by hand. The easiest would be to simply run it from a git
Mark> hook. patchwork comes with a simple script that just calculates the
Mark> hash a
On 2024-05-01 16:53, Tom Tromey via Overseers wrote:
> Mark> See also https://sourceware.org/bugzilla/show_bug.cgi?id=30997
> Mark> We really should automate this. There are several people running
> Mark> scripts by hand. The easiest would be to simply run it from a git
> Mark> hook. patchwork
Hi Jason,
On Wed, May 01, 2024 at 04:04:37PM -0400, Jason Merrill wrote:
> On 5/1/24 12:15, Jeff Law wrote:
> >We're currently using patchwork to track patches tagged with
> >RISC-V. We don't do much review with patchwork. In that model
> >patchwork ultimately just adds overhead as I'm constantl
On 5/1/24 2:04 PM, Jason Merrill wrote:
On 5/1/24 12:15, Jeff Law wrote:
On 4/22/24 9:24 PM, Tom Tromey wrote:
Jason> Someone mentioned earlier that gerrit was previously tried
Jason> unsuccessfully.
We tried it and gdb and then abandoned it. We tried to integrate it
into the traditional
On Wednesday, May 01 2024, Mark Wielaard wrote:
[...]
> But the part that interests me most is the self-registration part that
> Sergio setup. I believe we will need that for whatever system we end
> up with to make it as easy to contribute as it is with email.
> https://blog.sergiodj.net/posts/in
Snapshot gcc-11-20240501 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/11-20240501/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 11 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
> Do you (or others) have any thoughts about GitLab FOSS?
Dunno about the FOSS edition specifically, but I've used many review
tools in anger in the last 5 years: github, gitlab, gerrit, phabricator,
and a couple that ran in bugzilla ("MozReview", not sure if it had some
other name; and a second o
On Wed, May 1, 2024 at 11:41 PM Jeff Law via Gcc wrote:
>
>
>
> On 5/1/24 2:04 PM, Jason Merrill wrote:
> > On 5/1/24 12:15, Jeff Law wrote:
> >>
> >>
> >> On 4/22/24 9:24 PM, Tom Tromey wrote:
> >>> Jason> Someone mentioned earlier that gerrit was previously tried
> >>> Jason> unsuccessfully.
> >
14 matches
Mail list logo
