On Wed, 13 Dec 2023, 19:37 Thomas Schwinge, wrote:
> Hi!
>
> On 2023-12-13T11:15:54-0800, Jerry D via Gcc wrote:
> > I am getting this failure to build from clean trunk.
>
> This is due to commit r14-6499-g348874f0baac0f22c98ab11abbfa65fd172f6bdd
> "libgomp: basic pinned memory on Linux", which
On Wed, 13 Dec 2023 at 20:56, Thomas Schwinge wrote:
>
> Hi!
>
> On 2023-12-13T20:27:44+0000, Jonathan Wakely wrote:
> > On Wed, 13 Dec 2023, 19:37 Thomas Schwinge, wrote:
> >> On 2023-12-13T11:15:54-0800, Jerry D via Gcc wrote:
> >> > I am getting
On Tue, 9 Jan 2024 at 15:33, Ovais Khan via Gcc-help
wrote:
>
> Hello GCC Project Person,
> I would like to install the latest version of gfortran compiler for
> windows 10 on my computer.
> Could you please provide me with the weblink to download the file and
> necessary instructions to install i
On Thu, 18 Apr 2024 at 07:06, Thomas Koenig via Gcc wrote:
>
> Am 18.04.24 um 01:27 schrieb Mark Wielaard:
> > We also should make sure that all generated files (either in git or in
> > the release/snapshot tar balls) can be reliably and reproducibly
> > regenerated. This also helps the (pre-commi
On Mon, 29 Jul 2024 at 09:20, Thomas Koenig via Gcc wrote:
>
> Hi,
>
> for the fortran-unsigned branch, I would like to be able to run all
> existing Fortran tests also with -funsigned, to make sure the option
> does not break anything on existing code.
>
> Question is: How?
>
> I came as far as
>
On Mon, 29 Jul 2024 at 10:20, Jonathan Wakely wrote:
>
> On Mon, 29 Jul 2024 at 09:20, Thomas Koenig via Gcc wrote:
> >
> > Hi,
> >
> > for the fortran-unsigned branch, I would like to be able to run all
> > existing Fortran tests also with -funsigned, to mak
On Mon, 23 Sept 2024 at 16:20, Florian Weimer wrote:
>
> * Jonathan Wakely:
>
> > The discussion is about how we do patch submission and patch review.
> > The GitHub pull request workflow is widely seen as simpler than our
> > current email-based workflow (not everyb
On Mon, 23 Sept 2024 at 19:00, Eric Gallager via Gcc wrote:
>
> On Mon, Sep 23, 2024 at 8:09 AM Thomas Koenig via Gcc
> wrote:
> >
> > [For the fortran people: Discussion on gcc@]
> >
> > Just a general remark.
> >
> > There are people, such as myself, who regularly mess up
> > their git reposit
On Mon, 23 Sept 2024 at 14:36, enh wrote:
>
> it doesn't make the patch _management_ problem better ("now i have two
> problems"), but https://github.com/landley/toybox takes the "why not both?"
> approach --- you can use pull requests if you grew up with/adapted to
> git/github, or you can use
On Mon, 23 Sept 2024 at 13:09, Thomas Koenig via Gcc wrote:
>
> [For the fortran people: Discussion on gcc@]
>
> Just a general remark.
>
> There are people, such as myself, who regularly mess up
> their git repositories because they have no mental model
> of what git is doing
I highly recommend
On 27/12/22 08:33 -0800, H.J. Lu wrote:
On Sun, Dec 25, 2022 at 4:58 PM Steve Kargl via Gcc-patches
wrote:
On Wed, Dec 21, 2022 at 07:27:11PM -0500, Lipeng Zhu via Fortran wrote:
> This patch try to introduce the rwlock and split the read/write to
> unit_root tree and unit_cache with rwlock in
On Sun, 9 Feb 2025, 09:08 Thomas Koenig via Gcc, wrote:
> Hello world,
>
> looking at a few Fortran bug reports, I found some cases where
> it was not clear if the program in question was standard-conforming
> or not. I would propose to add a keyword for that, tentatively
> called "interp".
>
>
On Sun, 16 Mar 2025, 22:16 Mark Wielaard, wrote:
> Hi Harald,
>
> On Sun, Mar 16, 2025 at 10:57:08PM +0100, Harald Anlauf wrote:
> > I have never tried any complex setups besides simple ssh tunnels
> > with git in the past, so believe this does not apply.
> >
> > Doing even a simple ssh -Tvv to g
On Sun, 16 Mar 2025 at 21:30, Harald Anlauf via Gcc wrote:
> since I am experiencing extreme (temporary) performance problems
> again with a recently increased frequency and only during evening
> hours in Europe, I am asking if this is still the same cause.
>
> Today I've been waiting for hours fo
On Wed, 4 Jun 2025 at 16:43, Frank Ch. Eigler via Gcc wrote:
>
> Jerry D writes:
>
> > I am getting this tonight.
> > [...]
> > 257 | __gthread_cond_t _M_cond = __GTHREAD_COND_INIT;
>
> By the way, you can scan the sourceware.org buildbots, which include a
> broadish coverage of architectur
On Tue, 3 Jun 2025, 03:19 Jerry D via Gcc, wrote:
> I am getting this tonight.
>
This is a glibc change to the definition of PTHREAD_COND_INITIALIZER. It
looks like you updated glibc. A clean build should fix it.
> Jerry
>
> In file included from
>
> /home/jerry/dev/usr/include/c++/16.0.0/x8
On Tue, 11 Jan 2022 at 18:02, Harald Anlauf via Gcc wrote:
>
> Am 11.01.22 um 16:50 schrieb Martin Liška:
> > On 1/11/22 16:48, Toon Moene wrote:
> >> On 1/11/22 13:56, Martin Liška wrote:
> >>
> >>> Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
> >>> Plus it survives buil
On Mon, 13 Jun 2022 at 02:51, Wileam Yonatan Phan via Gcc
wrote:
>
> Hi everyone,
>
> This weekend marks the end of the community bonding period for GSoC '22, and
> here’s my progress so far with the GSoC project on Fortran DO CONCURRENT.
>
> I've initialized a GCC mirror on GitHub where I plan to
On Mon, 13 Jun 2022 at 14:34, Wileam Yonatan Phan wrote:
>
> Hi Jonathan,
>
> Thanks for the feedback. Regarding the linked page <
> https://gcc.gnu.org/wiki/InstallingGCC>
> if you're referring to the part that tells you to use your distro's package
> manager, yes that's indeed the simplest way to
On Mon, 13 Jun 2022, 18:12 Wileam Yonatan Phan,
wrote:
>
>
> Yes, you are correct that the script currently uses the tip of the
> `releases/gcc-[version]` branches. Is that not the same as using the
> published
> tarballs on the FTP server?
No.
I _do_ notice that these branches only get pushe
On Tue, 14 Jun 2022 at 01:37, Damian Rouson wrote:
>
>
>
> On Mon, Jun 13, 2022 at 8:27 AM Jonathan Wakely via Fortran
> wrote:
>>
>>
>> Yes, it does that, but takes 400 lines of shell script to do so.
>>
>> If you want "relatively easy ways t
On Fri, 17 Jun 2022 at 19:45, Bernhard Reutner-Fischer wrote:
>
> On 13 June 2022 17:26:59 CEST, Jonathan Wakely via Fortran
> wrote:
>
> >https://gist.github.com/jwakely/95b3a790157f55d75e18f577e12b50d7#file-build_gcc_versions-sh
>
> s/[[/[/
> s/==/=/
>
On Fri, 3 Feb 2023, 04:09 Andrew Pinski via Gcc, wrote:
> On Wed, Jan 25, 2023 at 1:07 PM Ben Boeckel via Fortran
> wrote:
> >
> > Hi,
> >
> > This patch series adds initial support for ISO C++'s [P1689R5][], a
> > format for describing C++ module requirements and provisions based on
> > the sou
On Fri, 3 Feb 2023 at 08:58, Jonathan Wakely wrote:
>
>
>
> On Fri, 3 Feb 2023, 04:09 Andrew Pinski via Gcc, wrote:
>>
>> On Wed, Jan 25, 2023 at 1:07 PM Ben Boeckel via Fortran
>> wrote:
>> >
>> > Hi,
>> >
>> > This patch series
On Fri, 20 Aug 2021 at 13:59, Arjen Markus wrote:
>
> Going the WSL2 route (I am not all that familiar with WSL) or a Linux
> emulation may be the way to go, indeed, but your remark triggered me to do a
> bit of searching: there is some discussion about the secure_getenv() function
> wrt Cygwin
On Fri, 20 Aug 2021 at 14:09, Jonathan Wakely wrote:
>
> On Fri, 20 Aug 2021 at 13:59, Arjen Markus wrote:
> >
> > Going the WSL2 route (I am not all that familiar with WSL) or a Linux
> > emulation may be the way to go, indeed, but your remark triggered me to do
> >
On Mon, 4 Oct 2021, 15:14 Jakub Jelinek via Gcc, wrote:
> On Mon, Oct 04, 2021 at 12:07:54PM +0200, Jakub Jelinek via Gcc wrote:
> > Or the last option would be to try to make libgfortran.so.5 ABI
> compatible
> > with both choices on powerpc64le-linux. From quick skimming of
> libgfortran,
> >
27 matches
Mail list logo
