[wwwdocs] Remove release-specific anchors from our release pages

We could not have kept these stable in any case (since HTML does not allow ids to start with a digit), though given how short these pages are I opted to simply remove the anchors. Committed. Gerald Index: gcc-3.2/index.html ===

[wwwdocs] Replace use of the border attribute on the main page by CSS

Applied. Gerald Index: gcc.css === RCS file: /cvs/gcc/wwwdocs/htdocs/gcc.css,v retrieving revision 1.53 diff -u -r1.53 gcc.css --- gcc.css 26 Aug 2018 12:40:20 - 1.53 +++ gcc.css 26 Aug 2018 18:53:41 - @@ -36,6

Fix MIPS builds

MIPS builds have been failing to build due to trying to use an incomplete struct function type. The uses are coming from cfg.h which typically isn't included in the target files. Fixed by including "backend.h" and removing the "cfg.h" inclusion. THere's likely other targets (aarch64?) that

[PATCH 3/3] or1k: gcc: initial support for openrisc

-mm-dd Stafford Horne Richard Henderson gcc/ChangeLog: * common/config/or1k/or1k-common.c: New file. * config/or1k/*: New. * config.gcc (or1k*-*-*): New. * configure.ac (or1k*-*-*): New test for openrisc tls. * configure: Regenerated.

[PATCH 2/3] or1k: testsuite: initial support for openrisc

-mm-dd Stafford Horne Richard Henderson gcc/testsuite/ChangeLog: * gcc.c-torture/execute/20101011-1.c: Adjust for OpenRISC. * gcc.dg/20020312-2.c: Likewise. * gcc.dg/attr-alloc_size-11.c: Likewise. * gcc.dg/builtin-apply2.c: Likewise.

[PATCH 1/3] or1k: libgcc: initial support for openrisc

-mm-dd Stafford Horne Richard Henderson libgcc/ChangeLog: * config.host: Add OpenRISC support. * config/or1k/*: New. --- libgcc/config.host| 13 +++ libgcc/config/or1k/crti.S | 37 ++ libgcc/config/or1k/crtn.S | 33

[PATCH 0/3] OpenRISC port

Hello, Since February this year I have been working on an OpenRISC clean room rewrite. http://stffrdhrn.github.io/software/embedded/openrisc/2018/02/03/openrisc_gcc_rewrite.html As per the article, the old port had issues with some of the owners signing over FSF copyright. To get around

[PING] [PATCH] Fix not properly nul-terminated string constants in JIT

Ping... This is just plain wrong, independent of any STRING_CST semantic issues. The original patch (retested on current trunk) is here: https://gcc.gnu.org/ml/gcc-patches/2018-08/msg00370.html On 08/05/18 18:59, Bernd Edlinger wrote: > Hi! > > > My other patch with adds assertions to

[wwwdocs] index.html -- Use percent encodings in Bugzilla queries

Use percent encodings (%20, %5B, %5D) instead of verbatim ' ', '[', ']' and Bugzilla queries. Committed. Gerald Index: index.html === RCS file: /cvs/gcc/wwwdocs/htdocs/index.html,v retrieving revision 1.1092 retrieving revision

Re: [Patch][GCC] Document and fix -r (partial linking)

On Donnerstag, 23. August 2018 23:24:02 CEST Joseph Myers wrote: > On Thu, 23 Aug 2018, Iain Sandoe wrote: > > Joseph: As a side-comment, is there a reason that we don’t exclude > > gomp/itm/fortran/gcov from the link for -nostdlib / -nodefaultlib? > > > > If we are relying on the lib self-specs

Re: C++ PATCH for c++/87029, Implement -Wredundant-move

On Sun, Aug 26, 2018 at 09:57:32AM +1000, Jason Merrill wrote: > On Sat, Aug 25, 2018 at 5:34 AM, Marek Polacek wrote: > > On Fri, Aug 24, 2018 at 11:32:18PM +1000, Jason Merrill wrote: > >> On Fri, Aug 24, 2018 at 12:53 AM, Marek Polacek wrote: > >> > On Thu, Aug 23, 2018 at 10:44:30AM -0400,

[wwwdocs] faq.html - make HTML 5 ready

Replace the use of by ids. Remove the id of "bugreport" which was only used by GCC < 2.95.3. A number of cases here required special attention such as the very first one which originally read General information Committed. Gerald Index: faq.html

[wwwdocs] simtest-howto.html -- simplify/reduce explicit formatting

Another small step towards more general HTML (and thus HTML 5). If there is a strong desire to directly manage formatting, we can of course employ CSS. Appplied. Gerald Index: simtest-howto.html === RCS file:

[Patch, fortran] PRs 80477 and 86481 - memory leaks following function calls.

This patch grew from the original patch for PR80477 because it was found that the array valued version leaked memory as well. Then, I found that the assignment in class_result_9.f90 ICEd, while trying to fix the array valued test, class_result_8.f90. Finally, while I was about it, I fixed PR86481,

Re: [wwwdocs] */changes.html -- replace by id attributes

On Sun, 26 Aug 2018, Gerald Pfeifer wrote: > More of the same, though this a bit more involved since we cannot use > version numbers as ids (which may not start with a digit unfortunately). Plus two further ids "sanitized". Committed on top. Gerald Index: gcc-3.4/changes.html

Re: [PATCH] convert MIN_EXPR operands to the same type (PR 87059)

On Sat, Aug 25, 2018 at 12:13 PM, Jeff Law wrote: > On 08/24/2018 01:06 PM, Martin Sebor wrote: >> PR 87059 points out an ICE in the recently enhanced VRP code >> that was traced back to a MIN_EXPR built out of operands of >> types with different sign by expand_builtin_strncmp(). >> >> The

[wwwdocs] Simplify the formatting/coding of our main page a bit

...by omitting cellspacing from the navigation bar as well as the main pane. This doesn't make much of a difference; in fact makes things a little bit clearer even. Committed. Gerald Index: style.mhtml === RCS file:

[wwwdocs] */changes.html -- replace by id attributes

More of the same, though this a bit more involved since we cannot use version numbers as ids (which may not start with a digit unfortunately). Committed. Gerald Replace by id attributes. Use GCCX.Y instead of X.Y for ids since those must not start with a digit. Index: gcc-3.1/changes.html

[wwwdocs] news/profiledriven.html -- avoid

This updates news/profiledriven.html, where in addition to using id attributes we need to change the names of the ids since numbers are not acceptable. I decided to simply use "ref1" instead of "1" and so forth. Applied. Gerald Index: news/profiledriven.html

[wwwdocs] Use CSS instead of manual specifications for the width of items on our navigation bar

Remove explicit width specifications for items in the navigation bar; use CSS for that instead. (If we don't do that, individual items will not span the full width of the navigation bar; some of them indeed would be narrower.) Applied. Gerald Index: gcc.css

Re: [wwwdocs] Replace by id= attributes in all of projects/

On Sun, 29 Jul 2018, Gerald Pfeifer wrote: > ...and avoid a few that weren't referenced. > > This is the next step in cleaning up and simplifying our pages for > a transition to the (simpler) HTML 5. Turns out that also here there were a quite a few I missed, including some rather creative ones

Re: [Patch][GCC] Document and fix -r (partial linking)

On Dienstag, 21. August 2018 00:38:58 CEST Joseph Myers wrote: > On Fri, 3 Aug 2018, Allan Sandfeld Jensen wrote: > > > I think you're changing the wrong place for this. If you want -r to be > > > usable with GCC without using -nostdlib (which is an interesting > > > question), you actually need

Re: PING [PATCH] warn for strlen of arrays with missing nul (PR 86552, 86711, 86714) )

On 08/25/18 22:42, Martin Sebor wrote: > On 08/25/2018 01:32 PM, Bernd Edlinger wrote: >> On 08/25/18 21:02, Jeff Law wrote: >>> On 08/25/2018 12:36 PM, Bernd Edlinger wrote: >>> >>> >> >> Well, ya call it "layer one patch over the other" >> I call it "incremental improvements".

Re: [PATCH] Make strlen range computations more conservative

Hi, this is an update on my strlen range patch (V6). Again re-based and retested to current trunk. It finally removes the -ffassume-zero-terminated-char-arrays flag. And is more careful to preserve existing strlen optimization tests. I did not see the need to change the interface of

Re: [PATCH] Add a character size parameter to c_strlen/get_range_strlen

On 08/26/18 07:47, Jeff Law wrote: > On 08/21/2018 11:49 AM, Martin Sebor wrote: >> On 08/21/2018 09:44 AM, Joseph Myers wrote: >>> On Tue, 21 Aug 2018, Martin Sebor wrote: >>> Sure, but the only valid argument to %ls is wchar_t*.  Passing it something else is undefined. >>> >>> Well,

Re: [PATCH] Add a character size parameter to c_strlen/get_range_strlen

On 08/26/18 07:44, Jeff Law wrote: > On 08/21/2018 10:35 AM, Martin Sebor wrote: >> On 08/21/2018 09:59 AM, Jeff Law wrote: >>> On 08/21/2018 09:57 AM, Martin Sebor wrote: On 08/21/2018 02:59 AM, Richard Biener wrote: > On Tue, 21 Aug 2018, Bernd Edlinger wrote: > >> gcc -S -O2

Re: [PATCH] Use complete_array_type on flexible array member initializers

On 08/26/18 07:36, Jeff Law wrote: > On 08/24/2018 07:13 AM, Bernd Edlinger wrote: >> Hi! >> >> >> This patch prevents init values of STRING_CST and braced >> array initializers to reach the middle-end with incomplete >> type. >> >> This will allow further simplifications in the middle-end, >> and

Re: [PATCHv2] Call braced_list_to_string after array size is fixed

On 08/26/18 05:34, Jeff Law wrote: > On 08/24/2018 01:52 PM, Bernd Edlinger wrote: >> Hi, >> >> this updated patch fixes one regression with current trunk due >> to a new test case. Sorry for the confusion. >> >> The change to the previous version is: >> 1) the check to avoid folding on empty

Re: [PATCH] Add a character size parameter to c_strlen/get_range_strlen

On 08/23/2018 08:48 AM, Bernd Edlinger wrote: > On 08/23/18 16:24, Jeff Law wrote: >>> >>> Yes, and which one was the earlier, more controversial patch from me? >> >> https://gcc.gnu.org/ml/gcc-patches/2018-07/msg01800.html >> >> >> Which is the issue I'm working through right now :-) >> > >