From: Werner Almesberger <wa@almesberger.net>
To: lartc@vger.kernel.org
Subject: [LARTC] tcng version 8z
Date: Thu, 10 Oct 2002 23:45:55 +0000 [thread overview]
Message-ID: <marc-lartc-103429365320967@msgid-missing> (raw)
... is on SourceForge, http://tcng.sourceforge.net/#src
Besides a bunch of bug fixes, this release also contains a
greatly improved version of the comtc utility that copies
comments from the tcng source to tcc's "tc" output.
There are a few infrastructure changes to make comtc work
smoothly:
- tcc's -E option is now called -Wexperror or -Wexppostopt,
respectively
- tcc has a _new_ -E option that makes it behave much like
gcc -E
- tcc also has a new option -f that is used to override the
input file
Some of the bug fixes are also significant:
- if_u32.c sometimes generated incorrect classifiers when using
meta fields (disabled by default)
- tcc and tcsim happily copied all file name arguments to cpp,
which would then equally happily overwrite the second file
Also, tcsim's "end" command now checks if there are any polled
devices with pending packets, and prints an error in this case.
The full change log is below, as usual.
By the way, there are now more than 1500 regression tests.
- Werner
---------------------------------- cut here -----------------------------------
Version 8z (10-OCT-2002)
------------------------
- tcc and tcsim allowed passing more than one file name to cpp, which treats
the second file name as output file (tests/tcng-8z)
- protocol support for u32 mis-attached subexpressions under new field root
(tests/protcomb)
- tests/htbquant and tests/tcstimstp did not probe if HTB is available before
using it
- tcsim stopped HTB timers before last packet was sent (tests/tcstimstp)
- tcsim now detects stopped devices with packets pending at "end"
(tests/tcstimstp)
- updated tests/basic, tests/tcssnap, tests/u32dlb, and tests/u32slb according
to above change
- -Wexpensive did not warn about implicit negation (tests/tcng-8z)
- tcc: replaced -E with -Wexperror, and -E -E with -Wexppostopt (tests/newexp)
- updated tests/bitfield, tests/bittest, tests/expensive, tests/ne,
tests/tcng-5y, and tests/tcng-7a according to above change
- tcc -E now runs cpp without any further processing (just like gcc -E;
tests/tccin)
- tcc: added option -f infile to read from specified file, ignoring input file
argument (tests/tccin)
- tcc now writes location map after dumping, in order to include
target-specific fixups in map
- added script toys/comtc that copies comments immediately preceding elements
to tc output (tests/comtc)
- runtests.sh: added command comtc to invoke toys/comtc
- tcc sometimes forgot that "prio" qdisc now supports policing (tests/tcng-8z)
- cleaned up hack causing compiler warning in if_u32.c
--
_________________________________________________________________________
/ Werner Almesberger, Buenos Aires, Argentina wa@almesberger.net /
/_http://www.almesberger.net/____________________________________________/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2002-10-10 23:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-10 23:45 Werner Almesberger [this message]
2002-10-11 12:18 ` [LARTC] tcng version 8z raptor
2002-10-11 13:45 ` Werner Almesberger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-lartc-103429365320967@msgid-missing \
--to=wa@almesberger.net \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.