[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [avr-libc-dev] How attached are people to the implementation of rand
From: |
George Spelvin |
Subject: |
Re: [avr-libc-dev] How attached are people to the implementation of rand()/random()? |
Date: |
7 Dec 2016 10:48:48 -0500 |
> I'd propose you use GCC trunk HEAD and Binutils master; if that and
> rerunning bootstrap does not do the trick, you found a bug and I
> wonder how the folks are testing avr-libc :-)
I'm working on compiling GCC trunk, but it has required a
little debugging. The build has failed a couple of times, and
$objdir/gcc/fixinc_list is getting created with the contents ";",
which causes an error at "make install" time.
Clearing that file makes the error go away and I have a working compiler,
but no <limits.h> file, which causes some later configure tests to fail.
But I can see one in $objdir/gcc/include-fixedlimits.h/limits.h and
manually copy it to $prefix/lib/gcc/avr/7.0.0/include-fixed
That seems to be working. Then I screwed myself up because I only did
"make clean; make" in the avr-libc directory and didn't re-run configure.
But after all that, I get lots of tests passing! Quite a few failures,
such as:
Simulate: regression/bug-22828.c atmega128 ... /tmp/cciW6XcS.o: In function
`main':
~/avr/avr-libc/avr-libc/tests/simulate/regression/bug-22828.c:50: undefined
reference to `eeprom_write_block'
~/avr/avr-libc/avr-libc/tests/simulate/regression/bug-22828.c:52: undefined
reference to `eeprom_read_block'
collect2: error: ld returned 1 exit status
*** compile failed
Simulate: regression/bug-25723.c atmega128 ... OK
Simulate: regression/bug-25723.c at90s8515 ... OK
Simulate: regression/bug-27235-1.c atmega128 ... OK
Simulate: regression/bug-27235-1.c at90s8515 ... OK
Simulate: regression/bug-27242.c atmega128 ... *** simulate failed: 8
Simulate: regression/bug-27242.c at90s8515 ... *** simulate failed: 8
Simulate: regression/bug-28135.c atmega128 ... OK
Simulate: regression/bug-28135.c at90s8515 ... OK
Simulate: regression/bug-31644.c atmega128 ... /tmp/cc1lM4bi.o: In function
`build_pwm_table':
~/avr/avr-libc/avr-libc/tests/simulate/regression/bug-31644.c:77: undefined
reference to `eeprom_read_word'
~/avr/avr-libc/avr-libc/tests/simulate/regression/bug-31644.c:79: undefined
reference to `eeprom_read_word'
~/avr/avr-libc/avr-libc/tests/simulate/regression/bug-31644.c:80: undefined
reference to `eeprom_read_word'
~/avr/avr-libc/avr-libc/tests/simulate/regression/bug-31644.c:81: undefined
reference to `eeprom_read_word'
~/avr/avr-libc/avr-libc/tests/simulate/regression/bug-31644.c:82: undefined
reference to `eeprom_read_word'
/tmp/cc1lM4bi.o:~/avr/avr-libc/avr-libc/tests/simulate/regression/bug-31644.c:83:
more undefined references to `eeprom_read_word' follow
collect2: error: ld returned 1 exit status
*** compile failed
Simulate: regression/bug-35093.c atmega128 ... OK
Simulate: regression/bug-35093.c at90s8515 ... OK
but it generally looks good.
One annoying error that pops up a lot is
Simulate: stdlib/dtostrf-01.c atmega128 ... In file included from
stdlib/dtostrf-01.c:36:0:
stdlib/dtostrf.h: In function 'run_dtostrf':
stdlib/dtostrf.h:99:8: warning: assignment discards 'const' qualifier from
pointer target type [-Wdiscarded-array-qualifiers]
pv = & pt->pattern;
^
OK
Simulate: stdlib/dtostrf-01.c at90s8515 ... In file included from
stdlib/dtostrf-01.c:36:0:
stdlib/dtostrf.h: In function 'run_dtostrf':
stdlib/dtostrf.h:99:8: warning: assignment discards 'const' qualifier from
pointer target type [-Wdiscarded-array-qualifiers]
pv = & pt->pattern;
^
OK
Simulate: stdlib/dtostrf-big.c atmega128 ... In file included from
stdlib/dtostrf-big.c:37:0:
stdlib/dtostrf.h: In function 'run_dtostrf':
stdlib/dtostrf.h:99:8: warning: assignment discards 'const' qualifier from
pointer target type [-Wdiscarded-array-qualifiers]
pv = & pt->pattern;
^
OK
I'll submit a patch for that.
- Re: [avr-libc-dev] How attached are people to the implementation of rand()/random()?, (continued)
- Re: [avr-libc-dev] How attached are people to the implementation of rand()/random()?, Georg-Johann Lay, 2016/12/06
- Re: [avr-libc-dev] How attached are people to the implementation of rand()/random()?, George Spelvin, 2016/12/06
- Re: [avr-libc-dev] How attached are people to the implementation of rand()/random()?, Georg-Johann Lay, 2016/12/06
- Re: [avr-libc-dev] How attached are people to the implementation of rand()/random()?, George Spelvin, 2016/12/06
- Re: [avr-libc-dev] How attached are people to the implementation of rand()/random()?, Georg-Johann Lay, 2016/12/06
- Re: [avr-libc-dev] Testsuite (Was: How attached are people ...), Joerg Wunsch, 2016/12/06
- Re: [avr-libc-dev] Testsuite (Was: How attached are people ...), Joerg Wunsch, 2016/12/06
- Re: [avr-libc-dev] Testsuite (Was: How attached are people ...), Georg-Johann Lay, 2016/12/07
- Re: [avr-libc-dev] Testsuite (Was: How attached are people ...), Joerg Wunsch, 2016/12/07
- Re: [avr-libc-dev] How attached are people to the implementation of rand()/random()?, Pitchumani Sivanupandi, 2016/12/07
- Re: [avr-libc-dev] How attached are people to the implementation of rand()/random()?,
George Spelvin <=
- Re: [avr-libc-dev] How attached are people to the implementation of rand()/random()?, Joerg Wunsch, 2016/12/07
- [avr-libc-dev] Testsuite (Was: How attached are people ...), George Spelvin, 2016/12/07
- Re: [avr-libc-dev] Testsuite (Was: How attached are people ...), Joerg Wunsch, 2016/12/07
- Re: [avr-libc-dev] Testsuite (Was: How attached are people ...), George Spelvin, 2016/12/07
- Re: [avr-libc-dev] Testsuite (Was: How attached are people ...), Joerg Wunsch, 2016/12/07