Re: gcc/DATESTAMP not updated any longer

On 12/11/20 7:26 PM, Jakub Jelinek wrote: When running it manually it just completed without problems. So, no idea what happened. Morning. Unfortunately, today we have similar problem. Master was bumped, but not any of the release branches: commit c5853240cdae1e727a65d1300e05307e5197bc69 (ori

Re: gcc/DATESTAMP not updated any longer

On Mon, Dec 14, 2020 at 09:59:22AM +0100, Martin Liška wrote: > On 12/11/20 7:26 PM, Jakub Jelinek wrote: > > When running it manually it just completed without problems. > > So, no idea what happened. > > Morning. > > Unfortunately, today we have similar problem. Master was bumped, but > not any

Re: gcc/DATESTAMP not updated any longer

On 12/14/20 10:05 AM, Jakub Jelinek wrote: Note, last night r11 DATESTAMP bump actually succeeded, it was the other branches that failed. I know. So please try to output the script output to a log. So that we can analyze for the next time. Thanks, Martin

Re: gcc/DATESTAMP not updated any longer

On Mon, Dec 14, 2020 at 10:21:15AM +0100, Martin Liška wrote: > On 12/14/20 10:05 AM, Jakub Jelinek wrote: > > Note, last night r11 DATESTAMP bump actually succeeded, it was the other > > branches that failed. > > I know. > > So please try to output the script output to a log. So that we can anal

Re: gcc/DATESTAMP not updated any longer

On 12/14/20 10:23 AM, Jakub Jelinek wrote: On Mon, Dec 14, 2020 at 10:21:15AM +0100, Martin Liška wrote: On 12/14/20 10:05 AM, Jakub Jelinek wrote: Note, last night r11 DATESTAMP bump actually succeeded, it was the other branches that failed. I know. So please try to output the script output

Re: gcc/DATESTAMP not updated any longer

On Dez 14 2020, Martin Liška wrote: > On 12/11/20 7:26 PM, Jakub Jelinek wrote: >> When running it manually it just completed without problems. >> So, no idea what happened. > > Morning. > > Unfortunately, today we have similar problem. Master was bumped, but > not any of the release branches: Pe

Re: gcc/DATESTAMP not updated any longer

On Mon, Dec 14, 2020 at 11:02:44AM +0100, Andreas Schwab wrote: > On Dez 14 2020, Martin Liška wrote: > > > On 12/11/20 7:26 PM, Jakub Jelinek wrote: > >> When running it manually it just completed without problems. > >> So, no idea what happened. > > > > Morning. > > > > Unfortunately, today we h

Mail delivery failed: returning message to sender

This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: gcc@gcc.gnu.org host gcc.gnu.org [8.43.85.97] SMTP error from remote mail serve

Pytest usage in DejaGNU?

Hello. GCOV tests suffer from tests that would cover the intermediate format. It's a JSON format and and I'm attaching an example of its output. I would really like to use Python to make more complex tests: $ cat test_json.py import pytest import json def test_gcov_output(): data = json.lo

Re: [EXTERNAL]Re: MIPS Maintainer

Hi Maciej, > > >  Well, it's up to the GCC steering committee really to appoint > > > maintainers > > > , however you can post patches and > > > help > > > with getting reviews through right away.  There hasn't been much traffic > > > with the MIPS port rece

Re: Pytest usage in DejaGNU?

On 12/14/20 9:02 AM, Martin Liška wrote: > Hello. > > GCOV tests suffer from tests that would cover the intermediate format. > It's a JSON format and and I'm attaching an example of its output. > > I would really like to use Python to make more complex tests: > > $ cat test_json.py > import pyte

Re: cacheflush.2

On 12/11/20 11:14 AM, Alejandro Colomar (man-pages) via Gcc wrote: It looks like GCC recently moved from 'char *' to 'void *'. This SO question[1] (4 years ago) quotes the GCC docs and they had 'char *'. __builtin___clear_cache in GCC has always been declared to take void*. The signature in th

Re: Pytest usage in DejaGNU?

On Mon, 14 Dec 2020, Martin Liška wrote: > +spawn -noecho pytest -rA -s --tb=no $script "pytest" might not be the right command everywhere. If I install python3-pytest on Ubuntu 20.04 I only get /usr/bin/pytest-3 not /usr/bin/pytest. There is a clear advantage to any usage of Python only

Re: Pytest usage in DejaGNU?

On 12/14/20 10:21 PM, Joseph Myers wrote: > On Mon, 14 Dec 2020, Martin Liška wrote: > >> +spawn -noecho pytest -rA -s --tb=no $script > > "pytest" might not be the right command everywhere. If I install > python3-pytest on Ubuntu 20.04 I only get /usr/bin/pytest-3 not > /usr/bin/pytest.

Re: cacheflush.2

Hello Martin, Thanks for the correction! Then the prototypes that changes from 'char *' to 'void *' in r269082 were not exposed to the user, right? I guess then those are just internal implementation where GCC did use 'char *'. Where is the actual prototype exposed to the user declared? Thanks,

Re: gcc/DATESTAMP not updated any longer

On Fri, 11 Dec 2020, Martin Liška wrote: > On 12/11/20 2:17 PM, Rainer Orth wrote: > > Rainer Orth writes: > > > > > I noticed that gcc/DATESTAMP isn't updated any longer after this > > > Friday. I doubt this is intentional... > > > > This has happened again tonight... > > > > Rainer > >

Re: gcc/DATESTAMP not updated any longer

On Mon, 14 Dec 2020, Martin Liška wrote: > On 12/11/20 7:26 PM, Jakub Jelinek wrote: > > When running it manually it just completed without problems. > > So, no idea what happened. > > Morning. > > Unfortunately, today we have similar problem. Master was bumped, but > not any of the release bran