how to support GCC ?
Hello list, i work for a companie that is heavy user of gcc C-compiler (Intel &arm). We were ask for projects and i would like to support the C-compiler. (not personaly but providing support for a project). Does someone feel competent so we can discuss what is doable ? (e.g. I would have to provide clear goals and what advantages the companie has from that). I am not a list member so please reply directly.
Re: Test with an lto-build of libgfortran.
On 28/09/2023 20:59, Toon Moene wrote: On 9/28/23 21:26, Jakub Jelinek wrote: It is worse than that, usually the LTO format changes e.g. any time any option or parameter is added on a release branch (several times a year) and at other times as well. Though, admittedly GCC is the single package that actually could get away with LTO in lib*.a libraries, at least in some packagings (if the static libraries are in gcc specific subdirectories rather than say /usr/lib{,64} or similar and if the packaging of gcc updates both the compiler and corresponding static libraries in a lock-step. Because in that case LTO in there will be always used only by the same snapshot from the release branch and so should be compatible with the LTO in it. This might be an argument to make it a configure option, e.g. --enable-lto-runtime. This sort of thing should definitely Just Work for cross compilers and embedded platforms where the libraries are bundled with the compiler. Andrew
Check whether the global variable has been modified in a function or some blocks
Hi, I have recently been working on issues related to the changing values of global variables. That is, I was trying to develop a gimple pass, which needs to check whether the value of a global variable is modified in the a function or some blocks. Some of the more tricky cases are as follows: int type; // global variable void foo() { int tmp; tmp = type; // store type in tmp type = 0; // do other things // type will be used or changed // ... type = tmp; return; } Obviously, this function does not modify the value of type, but from the compiler's point of view, it seems not so obvious. I'd like to ask is there any good way to solve it? Or does gcc provide some ready-made implementations to use already?
gcc-12-20230929 is now available
Snapshot gcc-12-20230929 is now available on https://gcc.gnu.org/pub/gcc/snapshots/12-20230929/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 12 git branch with the following options: git://gcc.gnu.org/git/gcc.git branch releases/gcc-12 revision bc1e385488001b0bd1a9b9c55b09ce987c31d353 You'll find: gcc-12-20230929.tar.xz Complete GCC SHA256=c8ceafaeece2e0e88e500dddf7c3f238a97adefa211311e18d7f44711de187d8 SHA1=a2c832d1e2cd5ea56e194566232ed025328fd9e8 Diffs from 12-20230922 are available in the diffs/ subdirectory. When a particular snapshot is ready for public consumption the LATEST-12 link is updated and a message is sent to the gcc list. Please do not use a snapshot before it has been announced that way.
RT ET XX
Sent from my iPhone set t