Email or username:

Password:

Forgot your password?
2 posts total
sam

GCC 14 is still in development, but it has a wonderful new feature in its static analyzer (-fanalyzer).

It can now draw beautiful Unicode diagrams showing exactly how you went out-of-bounds.

See inbox.sourceware.org/gcc-patch too.

Thank you to the wonderful David Malcolm for implementing this - who also does a tonne of work with mentoring for GCC's GSoC programme, and working on docs to help new people get into GCC: gcc-newbies-guide.readthedocs..

@gnutools

GCC 14 is still in development, but it has a wonderful new feature in its static analyzer (-fanalyzer).

It can now draw beautiful Unicode diagrams showing exactly how you went out-of-bounds.

See inbox.sourceware.org/gcc-patch too.

Thank you to the wonderful David Malcolm for implementing this - who also does a tonne of work with mentoring for GCC's GSoC programme, and working on docs to help new people get into GCC: gcc-newbies-guide.readthedocs.

Show previous comments
sam

I should also say that if you want a distribution that makes it very easy to have multiple GCCs installed at once and is recognised for its high-quality toolchain maintenance, you know where we are ๐Ÿ˜‰

sam

Today, we changed the default recommended filesystem in the handbook from ext4 to xfs.

XFS is robust and has all the niceties of ext4 (modulo shrinking) but with modern features on top.

(It helps that xfsprogs doesn't have weird endianness bugs too..)

btrfs is of course another option for the future but our users are conservative in some respects, and baby steps > none.

The main benefit of this is reflinks and copy_file_range which automatically takes advantage of that.

Now, as for using it.. ๐Ÿงต

Today, we changed the default recommended filesystem in the handbook from ext4 to xfs.

XFS is robust and has all the niceties of ext4 (modulo shrinking) but with modern features on top.

(It helps that xfsprogs doesn't have weird endianness bugs too..)

btrfs is of course another option for the future but our users are conservative in some respects, and baby steps > none.

sam

Portage uses copy_file_range and friends when merging packages to the live filesystem when it can by providing wrappers of some Python stdlib functions.

If XFS (or another "good" backing fs is used), it can take advantage of it for you.

We've found a bunch of bugs over the years through this, in various filesystems, actually!

Take a look at wiki.gentoo.org/wiki/User:Sam/ for a list.

Go Up