Re: divmod pattern question

On Jun 19 2018, Paul Koning wrote: > I have a two-operand divide instruction that takes a double length dividend > in a register pair, and produces the quotient in the first register and > remainder in the second. That's looks like the m68k div insn. Andreas. -- Andreas Schwab, SUSE Labs, s

Re: Understanding tree_swap_operands_p wrt SSA name versions

On Wed, Jun 20, 2018 at 7:31 AM Jeff Law wrote: > > On 06/19/2018 12:30 PM, Michael Ploujnikov wrote: > > Hi everyone, > > > > (I hope this is the right place to ask, if not my apologies; please > > point me in the right direction) > > > > I'm trying to get a better understanding of the following

GCC gfortran doc : correction to documentation

Hello, I have been consulting the documentation for MINLOC: https://gcc.gnu.org/onlinedocs/gfortran/MINLOC.html Thank you for the work you do. I think that when the documentation reads " If more than one element in the array has the minimum value, the location returned is that of the first su

Re: divmod pattern question

> On Jun 20, 2018, at 1:16 AM, Jeff Law wrote: > > On 06/19/2018 12:55 PM, Paul Koning wrote: >> Gentlepeople, >> >> I have a two-operand divide instruction that takes a double length dividend >> in a register pair, and produces the quotient in the first register and >> remainder in the sec

Re: GCC gfortran doc : correction to documentation

CCing the gfortran list. On Wed, 20 Jun 2018 at 12:35, Fernando wrote: > > Hello, > > I have been consulting the documentation for MINLOC: > > https://gcc.gnu.org/onlinedocs/gfortran/MINLOC.html > > Thank you for the work you do. > > I think that when the documentation reads > > " > If more than o

Re: [GSOC] LTO dump tool project

Hi, Please find the diff file for dumping tree type stats attached here with. example: $ ../stage1-build/gcc/lto1 test_hello.o -fdump-lto-tree-type-stats Reading object files: test_hello.o integer_type3 pointer_type3 array_type1 function_type4 I have pushed the c

-Wno-format-contains-nul

Years and years ago, I went to a mess of trouble to implement this specialized warning so I would not have to see it anymore. I use a code generator that puts constant strings into one huge buffer with all the contained strings NUL separated. Today, I was trying to build on OS/X: libtool: compile

ICE in a testcase, not sure about solution

I'm running into an ICE in the GIMPLE phase, for gcc.c-torture/compile/386.c, on pdp11 -mint32. That's an oddball where int is 32 bits (due to the flag) but Pmode is 16 bits (HImode). The ICE message is: ../../gcc/gcc/testsuite/gcc.c-torture/compile/386.c: In function ‘main’: ../../gcc/gcc/tes

Re: -Wno-format-contains-nul

On Wed, Jun 20, 2018 at 11:17:50AM -0700, Bruce Korb wrote: > Years and years ago, I went to a mess of trouble to implement this > specialized warning so I would not have to see it anymore. I use a code > generator that puts constant strings into one huge buffer with all the > contained strings NUL

Re: -Wno-format-contains-nul

Thanks. I guess clang forked after the clever NUL-in-format-string was added, but before my fix. :( I'll add -Wno-format if I can identify clang over GCC. On Wed, Jun 20, 2018 at 11:32 AM Jakub Jelinek wrote: > On Wed, Jun 20, 2018 at 11:17:50AM -0700, Bruce Korb wrote: > > Years and years ago,

Next question: sizeof(char buf[2042])

Yeah, I guess this is Clang, but is it a legal interpretation for Clang? In file included from gnu-pw-mgr.c:24: In file included from ./fwd.h:288: *./seed.c:178:43: **warning: **sizeof on pointer operation will return size of 'const char *' instead of 'const char [2042]'* * [-Wsizeof-array

Re: Next question: sizeof(char buf[2042])

OK. My mistake. "Nevermind" -- side effect of another change. On Wed, Jun 20, 2018 at 11:47 AM Bruce Korb wrote: > Yeah, I guess this is Clang, but is it a legal interpretation for Clang? > > In file included from gnu-pw-mgr.c:24: > > In file included from ./fwd.h:288: > > *./seed.c:178:43: **wa

Re: Next question: sizeof(char buf[2042])

On Wed, Jun 20, 2018 at 11:47:45AM -0700, Bruce Korb wrote: > Yeah, I guess this is Clang, but is it a legal interpretation for Clang? > > In file included from gnu-pw-mgr.c:24: > > In file included from ./fwd.h:288: > > *./seed.c:178:43: **warning: **sizeof on pointer operation will return size

2019 MIPIM Yacht Charters

Experience Cannes in style on a Corporate Yacht Charter (https://u7419970.ct.sendgrid.net/wf/click?upn=FBDq8VEpDC2W9whzzZ5c9UJyWBG4s3G5UcA5SNxaxBVGA9wckcjt9k-2FbhUn2dI9YOr52YVi7UwEsDGMNmBD9Mw-3D-3D_iaYFtpR3d-2FR9fRvTiX3jMD42Aa63RX3G1cmVpk5p2CXwpUNZbHyoN4Gmkj0CQsf-2Brt7-2BnLgLPfxz3M0o1is-2FfpV3R01

Re: How to get GCC on par with ICC?

On Wed, Jun 6, 2018 at 11:57 AM, Joel Sherrill wrote: > > On Wed, Jun 6, 2018 at 10:51 AM, Paul Menzel < > pmenzel+gcc.gnu@molgen.mpg.de> wrote: > > > Dear GCC folks, > > > > > > Some scientists in our organization still want to use the Intel compiler, > > as they say, it produces faster code,

gcc-6-20180620 is now available

Snapshot gcc-6-20180620 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/6-20180620/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 6 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-6

Re: LTO and other test failures on trunk

On Mon, 2018-06-18 at 10:22 -0600, Martin Sebor wrote: > David, > > Have you been able to reproduce the jit test failures below on > tor? Is there some information I can get you from my builds to > help you debug it? Thanks for pointing it out. I've started seeing it on my machine. They appear