Re: gcc-wwwdocs branch python-formatting created. e1e17c97a8ae35cfb6b2f7428fb52b05f82450d1

On Sun, 1 Dec 2024, Alexander Monakov wrote: > You have to use the name of the branch in the remote repo, > "python-formatting": > > git push --delete origin python-formatting That did the job, thank you! On Sun, 1 Dec 2024, Mark Wielaard wrote: > I believe the correct invocation is: > > $ g

Re: gcc-wwwdocs branch python-formatting created. e1e17c97a8ae35cfb6b2f7428fb52b05f82450d1

On Fri, 23 Aug 2024, Eric Gallager wrote: >>> The branch, python-formatting has been created >>> at e1e17c97a8ae35cfb6b2f7428fb52b05f82450d1 (commit) >> Hmm, are you intentionally creating a branch for the wwwdocs repository >> (i.e., our web pages)? I don't recall us having used one befor

Re: We need to remove the Sphinx HTML docs

On Fri, 15 Nov 2024, Tamar Christina wrote: > FWIW, Even though I was one of those that really liked and wanted this > documentation update to sphinx, I agree with removing them as it is just > confusing or misleading to users at this point. > > I do hope that in the future we could try to moderni

PATCH for Re: new mirror greece

gmail.com >>>> Sponsor Name: Aristotle University of Thessaloniki >>>> Sponsor URL : https://auth.gr >>>> HTTP/HTTPS URL: fosszone.csd.auth.gr/gnu/gcc Thank you, Konstantinos. Here is the update I made to our mirrors page. Gerald commit 1b564590

Re: We need to remove the Sphinx HTML docs

On Fri, 15 Nov 2024, Jonathan Wakely wrote: > The HTML pages from Martin Liska's Sphinx doc experiment are still > online, and Google thinks they are the canonical locatiosn for GCC docs. ...which is really weird. I wonder what influenced Google's ranking here (all the more given that there shou

Re: We need to remove the Sphinx HTML docs

On Fri, 15 Nov 2024, Jonathan Wakely wrote: > All these directories should have been removed two years ago: Agreed. Thank you for digging into this and raising it, Jonathan! > $ ls -1 -d htdocs/onlinedocs/gcc/*/ > htdocs/onlinedocs/gcc/c-implementation-defined-behavior/ > htdocs/onlinedocs/gcc/ex

Re: Should we move the --param documention to gccint?

On Fri, 8 Nov 2024, Richard Sandiford via Gcc wrote: > We changed one of the AArch64-specific --params for GCC 14. > Unfortunately, it seems that a lot of people were relying on the > previous behaviour. Umpf. > Every --param is documented in the user-facing manual, so it's not > surprising that

[pushed] fortran: Minor fix to -ffrontend-optimize description (was: typo on homepage)

he Fortran parse tree. > > Might it be that it should say "... manipulating parts _of_ the Fortran > parse tree."? Yes, I believe you're right, so went ahead and pushed the following change. Thank you, Gerald commit a071fcda136d00f8321d0adc773007f4f45020ea Author: Gerald Pf

Re: gcc-wwwdocs branch python-formatting created. e1e17c97a8ae35cfb6b2f7428fb52b05f82450d1

On Mon, 19 Aug 2024, Eric Gallager via Gcc-cvs-wwwdocs wrote: > This is an automated email from the git hooks/post-receive script. It was > generated because a ref change was pushed to the repository containing > the project "gcc-wwwdocs". > > The branch, python-formatting has been created >

Re: smtgcc translation validation

On Sat, 30 Sep 2023, Krister Walfridsson via Gcc wrote: > I have now released the new implementation for translation validation I talked > about at the GNU Tools Cauldron last week: > https://github.com/kristerw/smtgcc Wouldn't it be appropriate/nice to promote this a bit more strongly from gcc

Re: Simple GCC projects page

On Tue, 20 Mar 2018, Christopher Higgs via gcc wrote: > If this belongs in a different mailbox, please let me know where it > should be sent. This was the right address, though sadly it somehow fell through the cracks originally. > I would like to start contributing to GCC. In viewing the relev

Re: new mirror greece

On Thu, 29 Jun 2023, Konstantinos Draziotis via Gcc wrote: > I'd like to let you know that I have successfully set up a mirror > (http/https server) in Greece for gcc. Thank you, Konstantinos! > Location : Thessaloniki / Greece > Admin Name : K. A. Draziotis > Admin Email : drazi...

Re: [RFC] MAINTAINERS: require a BZ account field

On Wed, 3 Jul 2024, Sam James wrote: >> Now, a bigger question: Why would anyone need to know my gcc.gnu.org >> username (or e-mail address) in the Bugzilla context? > Isn't it answered in the original proposal? It makes CCing the committer > of a bisect result way easier. No, it's not. And no,

Re: [RFC] MAINTAINERS: require a BZ account field

On Mon, 24 Jun 2024, Jonathan Wakely via Gcc wrote: >> 1) MAINTAINERS should list a field containing either the gcc.gnu.org >> email in full, or their gcc username (bikeshedding semi-welcome); > I like the proposal. I'd say it should be fine to just put the gcc > username (without the @gcc.gnu.org

Re: Minor correction

On Sun, 2 Jul 2023, ppw0--- via Gcc wrote: > just wanted to let you know that while going over > https://gcc.gnu.org/onlinedocs/gcc/x86-Options.html , I've noticed > certain sections, namely haswell, broadwell, skylake, knl, knm, > skylake-avx512, cannonlake, icelake-client, icelake-server, casc

[committed] PATCH for Re: Stepping down as maintainer for ARC and Epiphany

so pushed the patch below. Gerald commit f94598ffaf5affbc9421ff230502357b07c55d9c Author: Gerald Pfeifer Date: Mon May 20 16:43:05 2024 +0200 MAINTAINERS: Update Joern Rennecke's status This is per his mail to gcc@gcc.gnu.org on 7 Jul 2023. ChangeLog: *

Re: GCC testing on FreeBSD

Hi Jonathan, On Fri, 26 Apr 2024, Jonathan Wakely wrote: > How are you testing on FreeBSD? > > When I build GCC trunk on FreeBSD 14.0 and try to run the libstdc++ > testsuite it fails due to lots of these errors: > > Excess errors: > /usr/local/bin/ld: /tmp//ccev946q.o: relocation R_X86_64_32 ag

Thomas Schwinge appointed co-maintainer of the nvptx backend

It's my pleasure to announce Thomas Schwinge as co-maintainer of the nvptx backend. Congratulations and Happy Hacking, Thomas! Please go ahead and update MAINTAINERS accordingly. Gerald (on behalf of the steering committee)

Re: "file name" vs "filename"

On Sun, 1 Apr 2018, Sandra Loosemore wrote: >> Our docs currently are about even and I think it would be good to >> settle on one? >> >>   % grep "filename" $GCC/gcc/doc/*.texi | wc -l >>   92 >>   % grep "file name" $GCC/gcc/doc/*.texi | wc -l >>   103 >> >> (Once

[wwwdocs] testing: Tweak the link to upstream FTensor (was: Anyone using FTensor to test GCC (or otherwise)?)

I did not try. I pushed the little patch below. Gerald commit b74309c36e59105ef0d8e0d91a85a5bfa884e175 Author: Gerald Pfeifer Date: Fri Feb 17 02:19:19 2023 +0100 Tweak the link to upstream FTensor. diff --git a/htdocs/testing/testing-ftensor.html b/htdocs/testing/testing-ftensor.html

Anyone using FTensor to test GCC (or otherwise)?

>From previous times we have FTensor https://gcc.gnu.org/testing/testing-ftensor.html documented as one of the ways to test GCC. Alas http://www.wlandry.net/Projects/FTensor has been down for a while, and there does not appear to be a new location? Is anyone actually still using FTensor to te

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

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

Renaming git master?

[ gcc-patches -> gcc ] On Mon, 29 Mar 2021, Jonathan Wakely wrote: >> [LLVM] renamed the 'master' branch. I'll adjust the link tomorrow. > Done by this patch, pushed to master (which I think we should rename). Did I miss any discussions? Our documentation at https://gcc.gnu.org/git.html still

Re: Revert Sphinx documentation [Was: Issues with Sphinx]

On Mon, 14 Nov 2022, Jonathan Wakely wrote: > I formatted my new region/endregion pragmas on one line because that > seemed to be how it should be done for rSt, e.g. we had: > > ``#pragma GCC push_options`` ``#pragma GCC pop_options`` > > But I think the attached patch is more correct for how we

Re: Revert Sphinx documentation [Was: Issues with Sphinx]

On Mon, 14 Nov 2022, Martin Liška wrote: > The situation with the Sphinx migration went out of control. The TODO > list overwhelmed me and there are road-blocks that can't be easily fixed > with what Sphinx currently supports. This migration was/is a huge and complex undertaking, and you have be

Re: Announcement: Porting the Docs to Sphinx - tomorrow

On Tue, 8 Nov 2022, Martin Liška wrote: > After the migration, people should be able to build (and install) GCC > even if they miss Sphinx (similar happens now if you miss makeinfo). My nightly *install* (not build) on amd64-unknown-freebsd12.2 broke (from what I can tell due to this - it's bee

Re: gcc.gnu.org/wiki/ – broken because /moin_static1910/ files fail with 404

On Fri, 11 Nov 2022, Mark Wielaard wrote: > I don't know how this happened, but I assume the moin_static1910 link > under /www/gcc/htdocs to the site-package MoinMoin/web/static/htdocs > somehow got misplaced. I added a symlink and all seems fine again. Thank you, Mark! I believe this was on me.

Re: unreachable intro to gcc page linked to on readings page

On Wed, 24 Aug 2022, Jonathan Wakely wrote: >> a broken link points to >> >> An introduction to GCC by Brian J. Gough. >> . http://www.network-theory.co.uk/gcc/intro/ > There are much more recent archived copies like > https://web.archive.org/web/20181113021321/http://www.network-theory.co.uk/g

Re: Reqister to become gcc mirror site

Hi Ceasar, On Tue, 22 Feb 2022, Ceasar Sun wrote: > We sent the follow message two weeks ago, buy didn't get response yet. > So, send this again  and sorry for the inconvenience ~ I am sorry this didn't see an answer earlier. It looks like you are actively mirroring our download site already? >

Re: Old installation docs

On Wed, 20 Oct 2021, Joseph Myers wrote: > Those should have been removed in GCC commit > 431d26e1dd18c1146d3d4dcd3b45a3b04f7f7d59, it seems that forgot to remove > the link in the HTML version. I'm surprised my link checker has not found this broken link; I'll need to look into that. Thanks f

Re: replacing the VRP threader

On Wed, 22 Sep 2021, Aldy Hernandez via Gcc wrote: > Well, it turns out we're considerably better than reported. > > Andrew just found a one-line change in the path solver that improves > our VRP threading goodness to 18.5% and our overall jump threading > gains to 1.28%. Would that make a great

Re: [TCWG CI] 471.omnetpp slowed down by 8% after gcc: Avoid invalid loop transformations in jump threading registry.

On Wed, 29 Sep 2021, Maxim Kuvyrkov via Gcc wrote: > Configurations that track master branches have 3-day intervals. > Configurations that track release branches — 6 days. If a regression is > detected it is narrowed down to component first — binutils, gcc or glibc > — and then the commit rang

Re: Aldy Hernandez and Andrew MacLeod as VRP maintainers

On Thu, 17 Jun 2021, Aldy Hernandez via Gcc wrote: > On 6/17/21 12:18 AM, Jeff Law wrote: >> I am pleased to announce that the GCC Steering Committee has appointed Aldy >> Hernandez and Ian MacLeod as maintainers for the VRP subsystem (EVRP, VRP, >> Ranger). > I don't know who this Ian is, but I'm

Re: Mailing list reconfiguration: VERP Sender: header affected

On Thu, 3 Jun 2021, Martin Liška via Overseers wrote: > On 6/2/21 4:52 PM, Frank Ch. Eigler via Gcc wrote: >> If you use Sender:-based filtering for sorting your incoming email >> stream, I suggest switching to observing List-Id: instead, or else >> using a regexp/substring style of Sender: matchin

Re: a small typo in the documentation, FYI

On Tue, 7 Jul 2020, Nino Pereira via Gcc wrote: > The top line in > https://gcc.gnu.org/onlinedocs/gcc-4.6.3/gfortran/BOZ-literal-constants.html > > says " The syntax is: `prefix quote digits quote', were the prefix is > either b, o or z," > > Here, 'were' must be 'where' Thank you for the repor

Re: Build failure in fixincludes on x86_64

On Wed, 26 May 2021, Richard Earnshaw via Gcc wrote: >> ../../git/gcc/fixincludes/fixtests.c: In function ‘run_test’: >> ../../git/gcc/fixincludes/fixtests.c:155:1: internal compiler error: >> in operator[], at vec.h:890 >> 155 | } >> | ^ > Same failure on arm. Same failure on x86 (32-bit,

Re: Links broken for C++ in web page "GCC online documentation: Latest releases"

On Wed, 28 Apr 2021, Pablo M. Ronchi via Gcc wrote: > https://gcc.gnu.org/onlinedocs/ > > under the subheadings: > > Latest releases > GCC 11.1 manuals: > > The following items have all their links broken (HTML,... tarball): > > ... > GCC 11.1 Standard C++ Library Manual (also in PDF or XM

Re: gcc-11-20210426 is now available

On Mon, 26 Apr 2021, GCC Administrator via Gcc wrote: > Snapshot gcc-11-20210426 is now available on > https://gcc.gnu.org/pub/gcc/snapshots/11-20210426/ > and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. Thanks for re-running the snapshot, Joseph, and updating the infra

Re: Has FSF stopped processing copyright paperwork

On Mon, 26 Apr 2021, Romain GEISSLER via Gcc wrote: > Few weeks later, I would like to know if anyone on the list knows if FSF is > still processing copyright assignment these days. Basically shall people > willing to sign one just have to be patient as processing is still on-going, > or if process

Re: removing toxic emailers

On Fri, 16 Apr 2021, Frosku wrote: > In my view, if people employed by a small number of American companies > succeed in disassociating GCC from GNU/FSF, which is representative of > the free software grassroots community I find this insistant focus by some on "American companies" interesting - a

Re: GCC association with the FSF

On Sat, 10 Apr 2021, Giacomo Tesio wrote: > In fact, the mail boxes of the Steering Committee's members are > stored on their corporate servers. You keep making statements which are simply wrong. None of my GCC-related e-mails touch the servers of my employer, nor servers under the control of my

Re: GCC association with the FSF

On Fri, 9 Apr 2021, Giacomo Tesio wrote: > GCC is clearly an US-only project. This is simply incorrect. > A US-corporate one. Totally SFW (in the US). As is this. > This is not intended as an insult. > It's just a fact. Ex falso quodlibet. Gerald

Re: GCC association with the FSF

On Sat, 10 Apr 2021, Richard Kenner via Gcc wrote: > I really think that most of the people replying on this thread have a > much more encompassing view of "GCC governance" than actually exists. There are a number of people arguing here who have contributed little to nothing to GCC, whose names e

Re: RMS removed from the GCC Steering Committee (was: Remove RMS...)

On Thu, 1 Apr 2021, Giacomo Tesio wrote: > Oh well, sure, but luckily the solution is just as fast and easy as > it was to remove RMS: pick just one person for each nationality and > remove the others. Why nationalities? That strikes me as a rather specific view focusing on one of many attributes

libstdc++-v3/doc/xml/manual/backwards_compatibility.xml

I noticed this section on "Backwards Compatibility" in the libstdc++ docs that talks about - glibc 2.0.x - GCC 3.2 (August 2002) - GCC 4.1 (February 2006) and links to "Migrating to GCC 4.1" and "Migration guide for GCC-3.2" documents. Does this still make sense (and serve real users or deve

Re: C++11 code in the gcc 10 branch

On Mon, 21 Dec 2020, FX via Gcc wrote: > I’m trying to bootstrap a GCC 10 compiler on macOS with clang, and I am > getting errors in stage 1, because there is C++11 code that is rejected > by clang (because the bootstrap involves compiling stage 1 with > -std=gnu++98, online on master (see top-l

More consistency for Git log messages?

Having spent a bit more time with GCC sources (as opposed to wwwdocs) recently and looking for prior art to guide me, I noticed there's a lot of options to specific the ChangeLog file(s) to use. And correspondingly a lot of inconsistency. Right now we seem to allow for 1. gcc/cp/ChangeLog 2.

arm-related links in need of updates

I noticed there's a couple of links on arm.com that changed recently (probably in the last month or so). Can you please help and get those updated? (Even those that redirect.) On http://gcc.gnu.org/gcc-10/changes.html https://developer.arm.com/docs/101028/0009/data-processing-intrinsics

Re: [IMPORTANT] ChangeLog related changes

On Mon, 1 Jun 2020, Jonathan Wakely via Gcc-patches wrote: > The libstdc++ manual is written in Docbook XML, but we commit both the > XML and generated HTML pages to Git. Sometimes a small XML file can > result in dozens of mechanical changes to the generated HTML files, > which we record in the Ch

0800-GIT-HELP: Doing a simple backport

I hope the offer by some of you to support people like me who Git appears to hate with a fervor still stands? ;-) And I volunteer to enhance our documentation if it appears useful. Usecase: I've got a patch approved and pushed to HEAD, and approved for active release branches - 13a46321516e2efd

Re: subversion status on gcc.gnu.org

On Fri, 20 Mar 2020, Frank Ch. Eigler via Overseers wrote: > Both svn: and ssh+svn: now work for your archeological needs. > Further, URLs such as > > https://gcc.gnu.org/viewcvs?rev=279160&root=gcc&view=rev > https://gcc.gnu.org/r123456 > > are mapped to gitweb searches that try to locate the ma

Re: text/x-* attachments strippe

On Mon, 9 Mar 2020, Thomas König wrote: > I also seem to have missed all discussion on this change (if there was > anything). I do not understand why such a huge change was implemented > that way, and who did this. Perhaos the person(s) responsible could > speak up about this. Let's be careful

Re: List-Id header being stripped

On Mon, 9 Mar 2020, Florian Weimer wrote: > So the difference is > > List-Id: > > vs > > List-Id: Gcc mailing list > > I guess now you need to perform a substring match. Or remove the string. Is that doable? (It does not add value, and "Gcc" is wrong spelling anyway.) Gerald

[committed] wwwdocs: New GCC mirror from Rabat, Morocco

On Sun, 5 Jan 2020, Gerald Pfeifer wrote: > Happy to have you as a mirror, and if you'd like to submit a patch > for https://gcc.gnu.org/mirrors.html that'd be great. Otherwise we > can create one. I applied this patch that I created on behalf of Sa

Re: git conversion in progress

On Wed, 22 Jan 2020, Jakub Jelinek wrote: >> The rsync.html page can be removed too, since that was a way to download >> the entire svn repo. With git clone, you get the entire repo, so rsync >> isn't needed anymore. > I disagree, it isn't just about downloading a svn repo, but mailing list > arch

Re: Add News-feed item for git transition

On Wed, 22 Jan 2020, Richard Earnshaw (lists) wrote: > We're missing a statement on the main news feed about the git transition. Lovely, thanks. Gerald PS: Lovely referring to you creating the patch, not the missing announcement. ;-)

Re: git conversion in progress

On Mon, 13 Jan 2020, Joseph Myers wrote: > In addition, once git.html is more complete (has the list of branches > added, at least) we need to update the GCC home page to link to the new > pages in place of those for SVN, redirect the old pages to the new ones, > and generally update references

Re: Updating "regression hunting" to the Git world (was: [wwwdocs] Adjustments of "regression hunting" instructions to the post-SVN world.)

On Mon, 20 Jan 2020, Jonathan Wakely wrote: >> If you have further updates to that page, please go ahead and >> simply make them (or let me know). > It still says "The following SVN commands are ..." Yes, that's another piece I'll tackle today/tomorrow. >> Also contrib/reghunt appears in need of

Re: New redirects for git

On Mon, 13 Jan 2020, Jakub Jelinek wrote: > Thanks to everybody who have helped with this. Thank you for putting this in place, Jakub! Gerald

Updating "regression hunting" to the Git world (was: [wwwdocs] Adjustments of "regression hunting" instructions to the post-SVN world.)

On Sun, 19 Jan 2020, Gerald Pfeifer wrote (on gcc-patches@): > With Git a clone carries the whole repository, so remove instructions > on obtaining a local copy of the repository and related instructions > on SVN usage. I just updated https://gcc.gnu.org/bugs/reghunt.html , mostly by

Re: [wwwdocs] Generalize instructions and remove notes on repository mirroring via rsync.

[ gcc-patches -> gcc ] On Sat, 18 Jan 2020, Gerald Pfeifer wrote: > Remove all references how to perform local checkouts, to SVN, and > mirroring the repository. Instead generalize descriptions since > with the move to Git syncing the repository with rsync and then > checking out

Re: git conversion in progress

On Thu, 16 Jan 2020, Jonathan Wakely wrote: > On Thu, 16 Jan 2020 at 09:55, Georg-Johann Lay wrote: >> Hi, the front page reads "Our sources are readily and freely available >> via SVN...", similar recommendation for SVN in > Yes, it's been said more than once that the web pages will be updated >

1-800-GIT-HELP: Fixing a commit message?

the ,v files; in SVN I believe we did not want to allow for fixing commit messages a posteriori -- how about our Git setup? Policy-wise and practically? Gerald == from gcc-patches == From: Gerald Pfeifer To: gcc-patc...@gcc.gnu.org Date: Thu, 16 Jan 2020 19:15:28 +0100 (CET) Subject

Re: Proposal for the transition timetable for the move to GIT

On Thu, 9 Jan 2020, Joseph Myers wrote: >> Is there any chance we could get one more trunk snapshot before the >> conversion starts -- even if that means firing up the snapshot process >> Friday? It'd be quite useful for the ongoing Fedora build testing. > I could run a snapshot manually. I was p

Re: Proposal for the transition timetable for the move to GIT

On Fri, 10 Jan 2020, Maxim Kuvyrkov wrote: > I was wrong re. r182541, I didn't notice that it is the first commit on > branch. This renders the analysis in favor of reposurgeon conversion, > not svn-git. Kudos for that statement, Maxim. And thanks a bunch for all the work you have been doing,

Re: New GCC mirror from Rabat, Morocco

Hi Sami, On Sun, 6 Oct 2019, Sami Ait Ali Oulahcen wrote: > We'd like to start mirroring the GCC. apologies, it appears none of us did get back to you last year? Happy to have you as a mirror, and if you'd like to submit a patch for https://gcc.gnu.org/mirrors.html that'd be great. Otherwise we

Re: http://www.netgull.com mirror broken

On Wed, 4 Dec 2019, Dan Allen wrote: > http://www.netgull.com has gcc snapshots and releases, but in the past > few weeks only the diffs are there - none of the actual source tarballs > are present. > > I am not sure how to get this message through to netball, but I figured > you had a better c

Re: GCC 7.5 Released

On Fri, 15 Nov 2019, Richard Biener wrote: >> I disabled snapshots from the GCC 7 branch on gcc.gnu.org. > Huh, I thought I did - I usually do this when creating the RC > (and I didn't see a new snapshot during the RC phase). ftp://gcc.gnu.org/pub/gcc/snapshots/7-20191107/ came after ftp://gcc.gnu

Re: GCC 7.5 Released

On Thu, 14 Nov 2019, Richard Biener wrote: > This is also the last release from the GCC 7 branch which > will receive no further fixes from now on. I disabled snapshots from the GCC 7 branch on gcc.gnu.org. (It appears you made that change in SVN and ~gccadmin/scripts on that machine, but not th

Re: Hello, I would like to know how to download gcc 9.2 in windows from here. https://ftp.gnu.org/gnu/gcc/gcc-9.2.0/ Thanks.

On Tue, 5 Nov 2019, Aditya Guharoy wrote: > I would like to know how to download gcc 9.2 in windows from here. > https://ftp.gnu.org/gnu/gcc/gcc-9.2.0/ We distribute source code, that in turn can then be built for various platforms (such as Windows). If you enter "gcc windows binary" in your favo

Re: git conversion of GCC wwwdocs repository

On Wed, 25 Sep 2019, Jonathan Wakely wrote: > I mean that there's not much value in having my past commits listed as > coming from various "different" authors: > > Jonathan Wakely > Jonathan Wakely > Jonathan Wakely > Jonathan Wakely > Jonathan Wakely > > All of those "identities" are the sa

Re: GCC wwwdocs move to git done

On Wed, 9 Oct 2019, Joseph Myers wrote: > I've done the move of GCC wwwdocs to git (using the previously posted and > discussed scripts), including setting up the post-receive hook to do the > same things previously covered by the old CVS hooks, and minimal updates > to the web pages dealing wit

Re: GCC Git hooks

On Mon, 16 Sep 2019, Joel Brobecker wrote: > You mean the email notification sent by the hooks when a commit > gets pushed? If yes, here is an example: > > https://www.sourceware.org/ml/gdb-cvs/2019-09/msg00041.html Thank you, Joel! I got a little worried how to best parse that ;-), but then Jos

Re: GCC Git hooks

On Sun, 15 Sep 2019, Joseph Myers wrote: > Apart from general review of the test conversion / conversion and hook > scripts, which everyone can do, I think the main thing would be to advise > on what needs to happen to avoid breaking the www.gnu.org copy of the site > and your HTML validation sy

Re: GCC Git hooks

On Sat, 14 Sep 2019, Jason Merrill wrote: > Separately, Joseph volunteered to deal with converting the gcc-www > repository to git and dealing with those hooks. This is great, thank you! I was absolutely going to join Cauldron this week, but something personal is consuming me all of this month

[wwwdocs PATCH] for Re: autovectorization in gcc

On Thu, 10 Jan 2019, Jonathan Wakely wrote: >> [ https://gcc.gnu.org/projects/tree-ssa/vectorization.html ] > I'm not disputing that there could be better documentation, but that > page is not the place to find it. That page should probably get a > notice added saying that the project is complete a

Renaming vec_step in tree-vect-loop.c (to fix build on powerpc/clang)

I have seen an increasing number of reports of GCC failing to build with clang on powerpc (on FreeBSD, though that's probably immaterial). Turns out that clang has vec_step as a reserved word on powerpc with AltiVec. We OTOH use vec_step s as a variable name in gcc/tree-vect-loop.c. The best ap

Re: Building libssp on a system without gets()

On Sun, 5 Aug 2018, Florian Weimer wrote: >> some folks in FreeBSD-land have worked to remove all uses of gets() >> and in fact the gets() function itself. >> >> Generally GCC builds just fine in such an environment, except for >> libssp where libssp/gets-chk.c has the following: >> >>char * >

Re: Old options in self tests?

On Thu, 4 Oct 2018, Anthony Green wrote: > I was building a C compiler from a source tree that does not include > the sources for the fortran front-end. It seems that this is no longer > supported, and the fortran sources must be available even if you're only > building C/C++. > > I'll stop st

Re: GCC 6.5 Status Report (2018-10-12)

Hi Jakub, On Fri, 12 Oct 2018, Jakub Jelinek wrote: > If you have regression bugfixes or documentation fixes that should be > still backported to the branch, please test them and check them in > before Friday, October 19th I'd like to push back https://gcc.gnu.org/ml/gcc-patches/2018-10/msg000

PATCH for Re: Broken mirror site

On Tue, 2 Oct 2018, David McCallum wrote: > At this time, your Canadian mirror site at http://gcc.parentingamerica.com/ > is broken. There is only a page with the text "It works!"... which appears > to be untrue. Thanks for letting us know, David! James, heads up! For now I committed the patch b

Re: Heads up: Our web pages are now HTML 5

On Mon, 3 Sep 2018, Gerald Pfeifer wrote: > PS: There are a few older pages that I'm going to give a bit more > love and care the coming week or so, and our main page is the only > one left XHTML for the time being - WIP. To give you all an update, the number of pages still requiri

Heads up: Our web pages are now HTML 5

As those of you watching gcc-patches@ will have noticed (or will notice beginning of your week), I was busy this weekend completing my project to convert the GCC web pages to HTML 5 (from previously XHTML). What does this mean for you? Really not a lot, practically, since most of the changes r

Building libssp on a system without gets()

Hi Jakub, some folks in FreeBSD-land have worked to remove all uses of gets() and in fact the gets() function itself. Generally GCC builds just fine in such an environment, except for libssp where libssp/gets-chk.c has the following: char * __gets_chk (char *s, size_t slen) { char

Re: bootstrap failure due to declaration mismatch in r260956

On Wed, 30 May 2018, Martin Sebor wrote: > I think your r260956 is missing the following hunk: If this fixes the bootstrap for you (also ran into this myself just now), can you please go ahead and commit? We can always sort out things later, if there are details to be tweaked, but fixing a bootst

[wwwdocs PATCH] for Re: Policy for reverting someone else commit?

On Sun, 20 May 2018, Richard Biener wrote: > IIRC there is a 24h rule that global maintainers can invoke. Not > sure if that is formally documented somewhere. Yes, we have a reversion policy; it is documented at https://gcc.gnu.org/develop.html And, after me just having applied the patch belo

[wwwdocs] PATCH for Re: Remove *.mirror.babylon.network

On Wed, 21 Mar 2018, Tim Semeijn wrote: > For the foreseeable future we will not be able to provide our mirrors > anymore. Could you please remove: > > nl.mirror.babylon.network > fr.mirror.babylon.network Thank you for letting us know, Tim, and your service in the past! Both are really appreciat

[cpp,doc] PATCH for Re: CPP documentation minor typo

patch below. Gerald 2018-04-02 Gerald Pfeifer * doc/cpp.texi (Variadic Macros): Fix line continuation in an example. Index: doc/cpp.texi === --- doc/cpp.texi(revision 259011) +++ doc/cpp.texi(

"file name" vs "filename"

And now to the most important question of all. ;-) Should we use "file name" or "filename" when referring to the name of a file? Our docs currently are about even and I think it would be good to settle on one? % grep "filename" $GCC/gcc/doc/*.texi | wc -l 92 % grep "file name" $GCC/gcc/doc

[wwwdocs] PATCH for Re: GCC mirror - Please read it

On Sat, 3 Feb 2018, BigSearcher Info wrote: > please let me know if you need the mirror I set for the GCC community > some weeks ago. Thank you for doing that and letting us know, and sorry for the delay in responding. I just added this to the official GCC mirrors list per the patch below. Chee

www.sgi.com/tech/stl/ is gone

...redirecting to a dummy page. Unfortunately there are a fair number of references in the libstdc++ docs, see below. I'll take care of anything outside of libstdc++; can you please have a look as far as the libstdc++ docs go? Gerald http://gcc.gnu.org/onlinedocs/libstdc++/faq.html □ ht

[wwwdocs] PATCH for Re: Create a new mirror

On Wed, 28 Feb 2018, KoDDoS Mirror wrote: > We added missing cronjob to update it. It should be updated in > less than 6 hours. Yep, it did. I just applied the patch below. Thank you for mirroring and letting us know! Gerald Index: mirrors.html ===

Re: Create a new mirror

Hi Martin, On Mon, 6 Nov 2017, KoDDoS Mirror wrote: > The mirror is setup. Here is a patch as I do not have write access to > push it. I was just going to commit the following patch (sorry for the delay), alas noticed your mirror does not seem to, umm, mirror? The expectation is that you'll mir

[PATCH] for Re: netgull.com mirror doesn't have gcc release .sig files.

On Tue, 8 Jul 2014, Richard Biener wrote: >> The reason you do not see .sig files on our netgull.com mirror is >> that it mirrors gcc.gnu.org, which does not carry those, whereas >> ftp.gnu.org and hence its mirrors has them. >> >> Richi, Jakub, can you also add those .sig files to the copies on >>

Re: Create a new mirror

Hi Martin, On Tue, 31 Oct 2017, KoDDoS Mirror wrote: > We would like to create a new mirror for GCC in Dronten, Netherlands. > > Can you let us know how to process? you can just ahead, and let us know (ideally with a patch against http://gcc.gnu.org/mirrors.html ); that's all then. :-) Cheers,

[wwwdocs] PATCH for Re: New mirror site

On Sat, 2 Sep 2017, Daniel Volchixin wrote: > URL: http://mirror.linux-ia64.org/gnu/gcc/ > Country/City: Russia / Novosibirsk > Contact email / name: dan...@volchixin.co.uk (Daniel Volchixin) Thank you for hosting this mirror, Daniel and letting us know. I added this to our mirrors page with the

Re: broken link on this page https://gcc.gnu.org/gcc-7/changes.html for link to "Profile Mode" page:

On Fri, 4 Aug 2017, Jonathan Wakely wrote: > Thanks for letting us know, I've fixed the link. Thanks, Jonathan. https://gcc.gnu.org/onlinedocs/gcc-7.1.0/libstdc++/manual/manual/profile_mode.html ^ Should we do something about "manual

Re: Remove broken GCC 7.1 GCJ manual links

Hi Krisztian, On Thu, 29 Jun 2017, Paczári Krisztián wrote: > GCJ has been removed from GCC 7.1, so these broken links should also be > removed from the documentation page (https://gcc.gnu.org/onlinedocs/) > and probably from the scripts generating them: "GCC 7.1 GCJ Manual (also > in PDF or Po

Re: [og7] Git branch "openacc-gcc-7-branch"

On Tue, 18 Jul 2017, Thomas Schwinge wrote: > This being a Git-only branch, should it nevertheless be listed on > , in the "Active Development Branches" > section, replacing "gomp-4_0-branch" there? I would say so (with an according note). Thanks for thinking of that

Re: Remove ca.mirror.babylon.network

On Sun, 16 Jul 2017, Tim Semeijn wrote: > We will soon decommission our Canadian mirror due to restructuring. > Please remove the following server from the mirror list: > > ca.mirror.babylon.network/gcc Thank for you the head-up, Tim. I applied the patch below to make this change accordingly. >

  1   2   3   4   5   6   7   8   9   >