On Fri, Mar 10, 2023, 14:00 Gerald Pfeifer wrote:
> On Fri, 10 Mar 2023, Sandra Loosemore wrote:
> > AFAIK we have not knowingly changed any specific requirements beyond the
> > stated 4.7 and 4.9 for PDF output, but it concerns me that nobody is
> > likely to be using versions that old on a
On Fri, Mar 3, 2023 at 10:14 PM Jerry D via Fortran wrote:
> I am certainly not a C++ expert but it seems to me this all begs for
> automatic finalization where one would not have to invoke free at all.
> I suspect the gfortran frontend is not designed for such things.
+1 for RAII
The reason would be to show that they continue to not ICE as they used to.
No go paths are just as useful as go paths.
On Sat, Mar 11, 2023, 10:57 Jeff Law wrote:
>
>
> On 2/16/23 01:16, Eric Botcazou via Gcc-patches wrote:
> >> This fixes dg.exp/stack-check-2.c, -7, 8, and -16.c, which is
On Thu, Feb 16, 2023, 11:10 LIU Hao via Gcc-patches
wrote:
>
> --
> Best regards,
> LIU Hao
>
Ping
>
On Tue, Feb 14, 2023, 05:42 Jonathan Yong via Gcc-patches <
gcc-patches@gcc.gnu.org> wrote:
> Attached patches OK?
Ping
On Wed, Feb 15, 2023, 08:45 Jonathan Yong via Gcc-patches <
gcc-patches@gcc.gnu.org> wrote:
> gcc/testsuite/ChangeLog:
>
> * gcc.target/i386/harden-sls-6.c: fix warning on LLP64
> targets.
>
> Attached patch OK?
Ping
On Sat, Feb 18, 2023, 17:32 Gerald Pfeifer wrote:
> That was a bit too much in terms of additions things. :-)
>
> Pushed.
>
> Gerald
> ---
> htdocs/gcc-12/changes.html | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/htdocs/gcc-12/changes.html
On Thu, Feb 16, 2023 at 3:16 AM Eric Botcazou wrote:
>
> > This fixes dg.exp/stack-check-2.c, -7, 8, and -16.c, which is great!
>
> Try the attached patch.
Well... that patch just marks all of the tests as unsupported. But
for example, the ones quoted above run, work, and pass. And when they
On Wed, Feb 15, 2023 at 10:24 AM Eric Botcazou via Gcc-patches
wrote:
>
> Hi,
>
> this is the incompatibility of -fstack-clash-protection with Windows SEH. Now
> the Windows ports always enable TARGET_STACK_PROBE, which means that the stack
> is always probed (out of line) so
On Fri, Jan 20, 2023 at 10:21 PM Jerry DeLisle via Fortran
wrote:
>
> Hi all,
>
> Similar to a patch I committed a while ago for Cygwin, the attached
> patch allows it to pass on the mingw version of gfortran.
>
> It is trivial.
>
> Ok for trunk?
>
> Regards,
>
> Jerry
ping
On Sat, Feb 11, 2023 at 3:52 AM Gerald Pfeifer wrote:
>
> On Sat, 11 Feb 2023, Jonathan Yong via Gcc-patches wrote:
> >> could you please close the corresponding BR too?:
> >> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108350
> > I can't close it, but I put a note that it has been committed.
>
ping
On Sat, Jan 28, 2023 at 1:16 PM Jonathan Yong <10wa...@gmail.com> wrote:
>
> Patch OK?
>
> gcc/testsuite/ChangeLog:
>
> * gcc.dg/pr65658.c: fix LLP64 test.
Is it too soon to ping again? :) I think Nixman needs some feedback as to
whether he's on the right track in addressing your concerns.
On Sun, Feb 5, 2023, 12:39 NightStrike wrote:
> Jakub, ping
>
> On Thu, Jan 26, 2023, 12:50 i.nixman--- via Gcc-patches <
> gcc-patches@gcc.gnu.org> wrote:
>
Jakub, ping
On Thu, Jan 26, 2023, 12:50 i.nixman--- via Gcc-patches <
gcc-patches@gcc.gnu.org> wrote:
> hello,
>
> could someone look at the patch attached please?
>
> https://gcc.gnu.org/pipermail/gcc-patches/2023-January/610392.html
>
On Tue, Jan 31, 2023 at 9:27 PM David Malcolm wrote:
>
> Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
> Pushed to trunk as r13-5615-gd03ae4be2c6d48.
>
> gcc/testsuite/ChangeLog:
> * gcc.dg/analyzer/call-summaries-2.c: Add
> dg-require-effective-target alloca.
>
On Sat, Jan 21, 2023, 18:59 Jerry D via Fortran wrote:
>
> Proposed ChangeLog entry using git gcc-commit-mklog:
>
> Author: Jerry DeLisle
> Date: Sat Jan 21 15:47:19 2023 -0800
>
> Revise the line end tests to pass on certain windows test environments
> which inject spurious /r
On Fri, Jan 20, 2023 at 1:40 PM Gaius Mulley via Gcc-patches
wrote:
>
> Richard Biener writes:
>
> > The following adjusts libgm2 to properly use the multilib build
> > infrastructure, thereby fixing the install with
> > --enable-version-specific-runtime-libs
> >
> > In particular config-ml.pl
On Wed, Jan 11, 2023 at 7:14 AM Jakub Jelinek wrote:
> I've committed following after regtesting it on x86_64-linux and i686-linux:
...
> +/* { dg-do run { target int32 } } */
Ah, I didn't realize you meant literally int32. I didn't see that as
a choice here:
On Wed, Jan 11, 2023 at 4:43 AM Jakub Jelinek wrote:
>
> On Wed, Jan 11, 2023 at 04:27:11AM -0500, NightStrike wrote:
> > On Wed, Jan 11, 2023 at 4:07 AM Jakub Jelinek wrote:
> > >
> > > On Wed, Jan 11, 2023 at 03:58:40AM -0500, NightStrike wrote:
> > > > On Fri, Jan 6, 2023 at 4:56 AM Jakub
On Wed, Jan 11, 2023 at 4:07 AM Jakub Jelinek wrote:
>
> On Wed, Jan 11, 2023 at 03:58:40AM -0500, NightStrike wrote:
> > On Fri, Jan 6, 2023 at 4:56 AM Jakub Jelinek via Gcc-patches
> > wrote:
> > > --- gcc/testsuite/gcc.dg/pr108308.c.jj 2023-01-06 10:43:45.793009294
> > > +0100
> > > +++
On Fri, Jan 6, 2023 at 4:56 AM Jakub Jelinek via Gcc-patches
wrote:
> --- gcc/testsuite/gcc.dg/pr108308.c.jj 2023-01-06 10:43:45.793009294 +0100
> +++ gcc/testsuite/gcc.dg/pr108308.c 2023-01-06 10:43:40.218090375 +0100
> @@ -0,0 +1,39 @@
> +/* PR target/108308 */
> +/* { dg-do run { target {
On Fri, Dec 23, 2022 at 7:00 PM Jonathan Yong via Gcc-patches
wrote:
>
> On 12/22/22 12:28, i.nix...@autistici.org wrote:
> > On 2022-12-22 12:21, Jonathan Yong wrote:
> >
> > hello,
> >
> >> On 12/16/22 19:20, Eric Botcazou wrote:
> The libgcc parts look reasonable to me, but I can't
On Fri, Oct 21, 2022 at 8:33 AM Jacek Caban via Gcc-patches
wrote:
>
> On 2022-10-21 11:44, Eric Botcazou via Libstdc++ wrote:
> >>>/How does this compare with Eric B's proposal at
> >>>/>>>/https://gcc.gnu.org/legacy-ml/gcc-patches/2019-06/msg01840.html ?
> >>>/>>//>>/My proposal was to
On Thu, Jan 6, 2022, 18:31 cqwrteur via Gcc-patches
wrote:
> When building GCC hosted on windows with Canadian/native compilation
> (host==target), the build scripts in GCC would override DLLs with each
> other. For example, for MinGW-w64, 32-bit DLLs would override 64 bits
> because build
On Thu, May 28, 2020, 4:25 PM David Malcolm via Gcc-patches <
gcc-patches@gcc.gnu.org> wrote:
> On Wed, 2020-05-27 at 22:27 -0300, Nicolas Bértolo wrote:
> > > New C++ source files should have a .cc extension.
> > > I hope that at some point we'll rename all the existing .c ones
> > >
On Tue, Apr 28, 2020 at 10:37 AM David Malcolm via Gcc-patches
wrote:
> I'm working on a rewrite of the region_model code for GCC 11 that I
> hope will fix these issues, and allow this warning to be reintroduced.
If that's the case, why remove the warning just to add it back? You
could leave it
26 matches
Mail list logo
