Re: ☠ Buildbot (Sourceware): gcc - failed configure (failure) (master)

2023-01-30 Thread Mark Wielaard
Hi Steve, On Sun, 2023-01-29 at 22:27 -0800, Steve Kargl via Gcc wrote: > Please remove the skull and cross bones in the subject line. That is the default "hazard symbol" buildbot uses if a build turns from success to failure. If you have a better suggestion you might want to contact upstream htt

Re: Buildbot (Sourceware): gcc - failed configure (failure) (master)

2023-01-30 Thread Thomas Koenig via Fortran
On 30.01.23 14:52, Mark Wielaard wrote: Hi Steve, On Sun, 2023-01-29 at 22:27 -0800, Steve Kargl via Gcc wrote: Please remove the skull and cross bones in the subject line. That is the default "hazard symbol" buildbot uses if a build turns from success to failure. If you have a better suggest

Re: Buildbot (Sourceware): gcc - failed configure (failure) (master)

2023-01-30 Thread Steve Kargl via Fortran
On Mon, Jan 30, 2023 at 03:46:30PM +0100, Thomas Koenig wrote: > On 30.01.23 14:52, Mark Wielaard wrote: > > Hi Steve, > > > > On Sun, 2023-01-29 at 22:27 -0800, Steve Kargl via Gcc wrote: > > > Please remove the skull and cross bones in the subject line. > > > > That is the default "hazard symbo

Testsuite, dejagnu

2023-01-30 Thread Harald Anlauf via Fortran
Dear Hackers, is there a way to check that a particular warning is emitted only once for a source code line instead of multiple times? It appears that by default dg-warn matches one or more times. Thanks, Harald

Re: Testsuite, dejagnu

2023-01-30 Thread Andrew Pinski via Fortran
On Mon, Jan 30, 2023 at 12:27 PM Harald Anlauf via Fortran wrote: > > Dear Hackers, > > is there a way to check that a particular warning is emitted only > once for a source code line instead of multiple times? > > It appears that by default dg-warn matches one or more times. One example of how t

Aw: Re: Testsuite, dejagnu

2023-01-30 Thread Harald Anlauf via Fortran
Hi Andrew, > Gesendet: Montag, 30. Januar 2023 um 22:13 Uhr > Von: "Andrew Pinski" > An: "Harald Anlauf" > Cc: "fortran" > Betreff: Re: Testsuite, dejagnu > > On Mon, Jan 30, 2023 at 12:27 PM Harald Anlauf via Fortran > wrote: > > > > Dear Hackers, > > > > is there a way to check that a partic

[PATCH] Fortran: prevent redundant integer division truncation warnings [PR108592]

2023-01-30 Thread Harald Anlauf via Fortran
Dear Fortranners, the subject says it all: in some cases we emit redundant integer division truncation warnings (2 or 4), where just one would have been sufficient. This is solved by using gfc_warning instead of gfc_warning_now. The testcase uses a suggestion by Andrew to verify that we get the d

Re: Buildbot (Sourceware): gcc - failed configure (failure) (master)

2023-01-30 Thread Gerald Pfeifer
On Mon, 30 Jan 2023, Steve Kargl via Gcc wrote: > Bingo. In the case of non-[a-zA-Z] characters in the > Subject (or Fromi or To) line, the spam folder is normally > named /dev/null. Hmm, so any digit, parenthesis, or bracket in the Subject, and mails gets to /dev/null? Or having an umlaut or o

Re: Buildbot (Sourceware): gcc - failed configure (failure) (master)

2023-01-30 Thread Steve Kargl via Fortran
On Mon, Jan 30, 2023 at 11:07:46PM +0100, Gerald Pfeifer wrote: > On Mon, 30 Jan 2023, Steve Kargl via Gcc wrote: > > Bingo. In the case of non-[a-zA-Z] characters in the > > Subject (or Fromi or To) line, the spam folder is normally > > named /dev/null. > > Hmm, so any digit, parenthesis, or bra