Re: Warning annoyances in list_read.c

> > If he added a new option affecting libgfortran, then he should > > fix up libgfortran. > > He didn't add the warning to specifically annoy fortran developers. > It is trivial to add seven gcc_fallthrough() or breaks for someone who > knows the code and the person who added the warning obviously

Re: GCC 5.4 Release Candidate available from gcc.gnu.org

Richard, > … If all goes well I'd like to release GCC 5.4 at the beginning of next > week. Would it be possible to apply the following patch --- ../5.4.0-RC/gcc/testsuite/c-c++-common/asan/sanity-check-pure-c-1.c 2012-12-13 00:04:22.0 +0100 +++ ../5_work/gcc/testsuite/c-c++-common/asan/

Re: bug report : gfortran E edit descriptor

> I have an trouble in E edit descriptor of gfortran. > This is a example. > (source file: test.f95) >program test >implicit none >real a,b >a=135.0 >b=1737.5 >write(*,*)a,b >write(*,'(e9.3,a,f7.1)')a,' ',b >write(*,'(1pe9.3,a,f7.1)')a

Re: gfortran: enabling specific warnings for a used but not set variable, and a set but not used variable

This is tracked by bugzilla pr61181 (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61181). As a general comment post concerning gfortran should go to fort...@gcc.gnu.org. Cheers, Dominique

Re: Action stamps

> For Jakub or anyone else wanting a key to associate a file with a commit, > they can decide for themselves > what date format they want to use and whether to bother with the user id. I > would think that if he is only > interested in commits on the trunk (and so should use log --first-parent),

Re: debug-early branch merged into mainline

This caused https://gcc.gnu.org/ml/gcc-bugs/2015-06/msg00602.html. TIA Dominique

Re: Regular darwin builds

Due to pr64625 I have looked more carefully to your logs and I did not see any entry for libgomp. Is it expected? TIA Dominique > Le 15 déc. 2014 à 22:11, FX a écrit : > > Hi all, > > I’ve set up daily builds and regtests on a darwin box. The results should > appear directly on gcc-testres

Re: Regular darwin builds

-dsym3 Description: Binary data > Le 16 déc. 2014 à 21:55, Mike Stump a écrit : > > On Dec 16, 2014, at 12:46 PM, Iain Sandoe wrote: >> >> On 16 Dec 2014, at 20:40, Dominique d'Humières wrote: >>> >>>> Another testsuite issue on darwin is that testsui

Re: Regular darwin builds

> Another testsuite issue on darwin is that testsuite doesn’t clean up the > .dSYM directories it generates. This gets really annoying on my autotester :( I have a patch for that, but Iain does not like it!-( Dominique

Re: Regular darwin builds

Is it again the difference between testing before or after install? Dominique > Le 16 déc. 2014 à 20:50, Iain Sandoe a écrit : > > > On 16 Dec 2014, at 19:38, Dominique d'Humières wrote: > >> Looking at your results for gcc 5.0, I see a lot of gcc.dg/ubsan/* fail

Re: Regular darwin builds

Hi FX, Thanks for doing that. Looking at your results for gcc 5.0, I see a lot of gcc.dg/ubsan/* failures I don’t see in my tests. Any idea why? Dominique > Le 15 déc. 2014 à 22:11, FX a écrit : > > Hi all, > > I’ve set up daily builds and regtests on a darwin box. The results should > app

Re: [patch, build] Restore bootstrap in building libcc1 on darwin

This was for x86_64-apple-darwin14. The patch also works for x86_64-apple-darwin10. Dominique > Le 6 déc. 2014 à 01:49, Dominique d'Humières a écrit : > > Bootstrap just finished with the patch. > > Thanks, > > Dominique

Re: [patch, build] Restore bootstrap in building libcc1 on darwin

Bootstrap just finished with the patch. Thanks, Dominique > Le 5 déc. 2014 à 23:47, Jakub Jelinek a écrit : > > On Fri, Dec 05, 2014 at 11:34:28PM +0100, Dominique Dhumieres wrote: >>> As I've tried to explain, that is IMHO wrong though. >>> If what you are after is the -B stuff too, then perh