Re: xtensa PR65730
On Sat, Apr 11, 2015 at 2:16 AM, augustine.sterl...@gmail.com wrote: > On Fri, Apr 10, 2015 at 1:18 PM, Max Filippov wrote: >> How can we have a mulsi3 pattern that don't get expanded until it's >> optimized, and only gets expanded to a call if it couldn't be optimized? > > I'm not completely sure, but I think you want to use OPTAB_LIB as you > described above, and eliminate the TARGET_MUL32 condition in the > pattern. In that case mull is emitted for normal uses of multiplication. -- Thanks. -- Max
Re: Need help to install C++ compiler
Hey Kumar. Just use your package manager. in terminal: yum search gcc-c++ Determine which version are available. Then run: yum install gcc-c++ You will need root access for the install step. If you want another version RPM’s can be found here: http://www.rpmfind.net/linux/rpm2html/search.php?query=gcc-c%2B%2B Best regards: Lars Nielsen Student Software developer @ Steinwurf > On 11 Apr 2015, at 05:08, Kumar Aditya wrote: > > Hello GCC team, > > Greetings... > > I am new user of Linux. I have RHEL 6.0 installed and want to run C++ > on my system but I do not know how. > > Please help me or let me know where to contact. > -- > > Thanks & Regards, > > Kumar Aditya > +919015142426
Re: Need help to install C++ compiler
On 11/04/15 04:08, Kumar Aditya wrote: > I am new user of Linux. I have RHEL 6.0 installed and want to run C++ > on my system but I do not know how. yum install gcc-c++. Andrew.
copyright assignment forms
Hello, I’m interested in submitting PRs on gfortran, voluntarily from time to time as my time permits. Thus, I’m contacting you to obtain the relevant forms. Regards, Ev. Drikos On Apr 10, 2015, at 12:31 PM, Mikael Morin wrote: > Le 08/04/2015 21:15, Evangelos Drikos a écrit : >> Right now I’m trying to debug some PRs that >> I’m backporting to gcc-4.8.4; one of them spoils the test case “sizeof.f90". >> > In any case, if you plan to work seriously on the gcc or gfortran code, > you should proceed with the copyright assignment formality. > The patch you submitted for PR59016 was already too complex, I think, to > be accepted without copyright assignment. > > Mikael
Re: How to extract types of variables and its uid?
On Friday 10 April 2015 01:00 PM, Richard Biener wrote: Or is there any other unique feature to distinguish between two tree types, >other than type uid? Depends on the definition of the equality relation. We have considered the file name and line number where the types are defined as a unique feature to distinguish between two tree types. Thanks a lot. :-) Regards, Swati
Re: GNAT User's Guide /onlinedocs broken? (was: Broken links on gcc.gnu.org/onlinedocs)
>> The following links are broken at gcc.gnu.org/onlinedocs/4.9.2. The >> corresponding 4.9.2-related links at gcc.gnu.org/onlinedocs are also broken: >>GCC 4.9.2 GNAT User's Guide (/onlinedocs/gcc-4.9.2/gnat_ugn_unw/) >>also in PDF (/onlinedocs/gcc-4.9.2/gnat_ugn_unw.pdf) >>or Postscript (/onlinedocs/gcc-4.9.2/gnat_ugn_unw.ps.gz) >>or an HTML tarball (/onlinedocs/gcc-4.9.2/gnat_ugn_unw-html.tar.gz) > > This is not just broken for GCC 4.9.2, but GCC 4.8.4 as well: > > https://gcc.gnu.org/onlinedocs/gcc-4.9.2/gnat_ugn_unw/ > https://gcc.gnu.org/onlinedocs/gcc-4.8.4/gnat_ugn_unw/ > > It does still work for GCC 4.9.1 and GCC 4.8.3: > > https://gcc.gnu.org/onlinedocs/gcc-4.9.1/gnat_ugn_unw/ > https://gcc.gnu.org/onlinedocs/gcc-4.8.3/gnat_ugn_unw/ > > > Arnaud, you updated maintainer-scripts update_web_docs_svn as > follows last year, might this be related? > > 2014-08-01 Arnaud Charlet > >* update_web_docs_svn: Simplify build of gnat_ugn. > > Is the patch below a proper fix? Your patch looks good to me. > Index: index.html > === > RCS file: /cvs/gcc/wwwdocs/htdocs/onlinedocs/index.html,v > retrieving revision 1.147 > diff -u -r1.147 index.html > --- index.html6 Feb 2015 22:27:38 -1.147 > +++ index.html10 Apr 2015 20:00:02 - > @@ -53,12 +53,12 @@ > > href="https://gcc.gnu.org/onlinedocs/gcc-4.9.2/gnat_rm.ps.gz";>PostScript > or > href="https://gcc.gnu.org/onlinedocs/gcc-4.9.2/gnat_rm-html.tar.gz";>an > HTML tarball) > -https://gcc.gnu.org/onlinedocs/gcc-4.9.2/gnat_ugn_unw/";>GCC > +https://gcc.gnu.org/onlinedocs/gcc-4.9.2/gnat_ugn/";>GCC > 4.9.2 GNAT User's Guide ( - > href="https://gcc.gnu.org/onlinedocs/gcc-4.9.2/gnat_ugn_unw.pdf";>also > + href="https://gcc.gnu.org/onlinedocs/gcc-4.9.2/gnat_ugn.pdf";>also > in PDF or - > href="https://gcc.gnu.org/onlinedocs/gcc-4.9.2/gnat_ugn_unw.ps.gz";>PostScript > or - > href="https://gcc.gnu.org/onlinedocs/gcc-4.9.2/gnat_ugn_unw-html.tar.gz";>an > + > href="https://gcc.gnu.org/onlinedocs/gcc-4.9.2/gnat_ugn.ps.gz";>PostScript > or + > href="https://gcc.gnu.org/onlinedocs/gcc-4.9.2/gnat_ugn-html.tar.gz";>an > HTML tarball) > href="https://gcc.gnu.org/onlinedocs/gcc-4.9.2/libstdc++/manual/";>GCC > 4.9.2 Standard C++ Library Manual ( @@ -137,12 +137,12 @@ > > href="https://gcc.gnu.org/onlinedocs/gcc-4.8.4/gnat_rm.ps.gz";>PostScript > or > href="https://gcc.gnu.org/onlinedocs/gcc-4.8.4/gnat_rm-html.tar.gz";>an > HTML tarball) > -https://gcc.gnu.org/onlinedocs/gcc-4.8.4/gnat_ugn_unw/";>GCC > +https://gcc.gnu.org/onlinedocs/gcc-4.8.4/gnat_ugn/";>GCC > 4.8.4 GNAT User's Guide ( - > href="https://gcc.gnu.org/onlinedocs/gcc-4.8.4/gnat_ugn_unw.pdf";>also > + href="https://gcc.gnu.org/onlinedocs/gcc-4.8.4/gnat_ugn.pdf";>also > in PDF or - > href="https://gcc.gnu.org/onlinedocs/gcc-4.8.4/gnat_ugn_unw.ps.gz";>PostScript > or - > href="https://gcc.gnu.org/onlinedocs/gcc-4.8.4/gnat_ugn_unw-html.tar.gz";>an > + > href="https://gcc.gnu.org/onlinedocs/gcc-4.8.4/gnat_ugn.ps.gz";>PostScript > or + > href="https://gcc.gnu.org/onlinedocs/gcc-4.8.4/gnat_ugn-html.tar.gz";>an > HTML tarball) > href="https://gcc.gnu.org/onlinedocs/gcc-4.8.4/libstdc++/manual/";>GCC > 4.8.4 Standard C++ Library Manual (
Re: copyright assignment forms
On Sat, Apr 11, 2015 at 3:23 AM, Evangelos Drikos wrote: > Hello, > > I’m interested in submitting PRs on gfortran, voluntarily from time to time > as my time permits. > > Thus, I’m contacting you to obtain the relevant forms. Sent off list. Ian
Re: [PATCH][www] Document versioning scheme for GCC 5 and up
On Wed, 13 Aug 2014, Richard Biener wrote: > The following aims to document the details of the versioning scheme we > intend to use for GCC 5 and up. > > Summary in non-html: Development of GCC 5 will happen as > GCC 5.0.0 (experimental), once we enter regression-fixing-only mode > (post-stage3) it will become GCC 5.0.1 (prerelease). The > GCC 5 release itself will be numbered GCC 5.1.0 and development > on the branch will continue as GCC 5.1.1 followed by a GCC 5.2.0 > release and GCC 5.2.1 branch development. Stage1 of GCC 6 will > bump us to GCC 6.0.0. Is the idea really to call the actual releases 5.1.0, 5.2.0 and so forth, or will those be labled 5.1, 5.2,...? Using the former for gcc/BASEVER etc. make sense. From a "marketing" perspective I would recommend the simpler 5.1, 5.2, etc. Gerald
Re: [PATCH][www] Document versioning scheme for GCC 5 and up
On April 11, 2015 9:23:18 PM GMT+02:00, Gerald Pfeifer wrote: >On Wed, 13 Aug 2014, Richard Biener wrote: >> The following aims to document the details of the versioning scheme >we >> intend to use for GCC 5 and up. >> >> Summary in non-html: Development of GCC 5 will happen as >> GCC 5.0.0 (experimental), once we enter regression-fixing-only mode >> (post-stage3) it will become GCC 5.0.1 (prerelease). The >> GCC 5 release itself will be numbered GCC 5.1.0 and development >> on the branch will continue as GCC 5.1.1 followed by a GCC 5.2.0 >> release and GCC 5.2.1 branch development. Stage1 of GCC 6 will >> bump us to GCC 6.0.0. > >Is the idea really to call the actual releases 5.1.0, 5.2.0 and >so forth, or will those be labled 5.1, 5.2,...? > >Using the former for gcc/BASEVER etc. make sense. From a "marketing" >perspective I would recommend the simpler 5.1, 5.2, etc. 5.1 Richard. >Gerald
