History log of /dflybsd-src/lib/libevtr/Makefile (Results 1 – 10 of 10)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
Revision tags: v6.4.0, v6.4.0rc1, v6.5.0, v6.2.2, v6.2.1, v6.3.0, v6.0.1
# 19d79046 21-Aug-2021 Sascha Wildner <saw@online.de>

Some trivial changes to better comply with strict aliasing. (2)

Now that the warnings are fixed, do not pass -fno-strict-aliasing
anymore.


Revision tags: v6.0.0, v6.0.0rc1, v6.1.0, v5.8.3, v5.8.2, v5.8.1, v5.8.0, v5.9.0, v5.8.0rc1, v5.6.3, v5.6.2, v5.6.1, v5.6.0, v5.6.0rc1, v5.7.0, v5.4.3, v5.4.2, v5.4.1, v5.4.0, v5.5.0, v5.4.0rc1, v5.2.2, v5.2.1, v5.2.0, v5.3.0, v5.2.0rc, v5.0.2, v5.0.1, v5.0.0, v5.0.0rc2, v5.1.0, v5.0.0rc1, v4.8.1, v4.8.0, v4.6.2, v4.9.0, v4.8.0rc, v4.6.1
# 0de090e1 07-Aug-2016 Matthew Dillon <dillon@apollo.backplane.com>

build - prepare for higher optimization levels

* Add NO_STRICT_ALIASING, NO_STRICT_OVERFLOW, and NO_WARRAY_BOUNDS
make variables as-needed.


Revision tags: v4.6.0, v4.6.0rc2, v4.6.0rc, v4.7.0, v4.4.3, v4.4.2, v4.4.1, v4.4.0, v4.5.0, v4.4.0rc, v4.2.4, v4.3.1, v4.2.3, v4.2.1, v4.2.0, v4.0.6, v4.3.0, v4.2.0rc, v4.0.5, v4.0.4, v4.0.3, v4.0.2, v4.0.1, v4.0.0, v4.0.0rc3, v4.0.0rc2, v4.0.0rc, v4.1.0, v3.8.2, v3.8.1, v3.6.3, v3.8.0, v3.8.0rc2, v3.9.0, v3.8.0rc, v3.6.2, v3.6.1, v3.6.0, v3.7.1, v3.6.0rc, v3.4.3, v3.4.2, v3.4.1, v3.4.0, v3.4.0rc, v3.5.0, v3.2.2, v3.2.1, v3.2.0, v3.3.0, v3.0.3, v3.0.2, v3.0.1, v3.1.0, v3.0.0
# 86d7f5d3 26-Nov-2011 John Marino <draco@marino.st>

Initial import of binutils 2.22 on the new vendor branch

Future versions of binutils will also reside on this branch rather
than continuing to create new binutils branches for each new version.


Revision tags: v2.12.0, v2.13.0, v2.10.1, v2.11.0, v2.10.0
# 04335f67 28-Feb-2011 Joe Talbott <josepht@dragonflybsd.org>

Merge branch 'master' of git://crater.dragonflybsd.org/dragonfly


# 102ec862 10-Feb-2011 Matthew Dillon <dillon@apollo.backplane.com>

Merge branch 'master' of ssh://crater.dragonflybsd.org/repository/git/dragonfly


# 2443e96e 07-Feb-2011 Justin C. Sherrill <justin@leaf.dragonflybsd.org>

Merge branch 'master' of ssh://crater.dragonflybsd.org/repository/git/dragonfly

Conflicts:
UPDATING


# 1d99ff55 06-Feb-2011 Sascha Wildner <saw@online.de>

lib: Move the definition of WARNS into lib/Makefile.inc.


Revision tags: v2.9.1, v2.8.2, v2.8.1, v2.8.0, v2.9.0, v2.6.3, v2.7.3
# b04d251d 24-Apr-2010 Sascha Wildner <saw@online.de>

evtr: ktrfmt.tab.h is not supposed to be installed to /usr/include.


Revision tags: v2.6.2, v2.7.2, v2.7.1, v2.6.1, v2.7.0, v2.6.0
# 2b130cb3 17-Mar-2010 Aggelos Economopoulos <aoiko@cc.ece.ntua.gr>

evtr: initial implementation of a DSL

libevtr:
- abstract out the hash table, convert to using uintptr_t's
internally
- move a bunch of fields and most of the error logic from
evtr to evtr_query

evtr: initial implementation of a DSL

libevtr:
- abstract out the hash table, convert to using uintptr_t's
internally
- move a bunch of fields and most of the error logic from
evtr to evtr_query
- don't try to resolve format strings to id's and reject
records that don't match early; this needs way more care
now that we might want to interpret the format strings
- start implementation of a minimal Domain Specific Language
- add the ability to filter based on the event type
- lots of fixes all around

evtranalyze:
- catch up w/ API changes in libevtr
- add toy 'stats' command

show more ...


# e7c0dbba 08-Feb-2010 Aggelos Economopoulos <aoiko@cc.ece.ntua.gr>

Bring in a simple event tracing library and POC utility

- Import libevtr, a library for abstracting access to an event stream.
libevtr uses its own dump format and can synthesize event attributes

Bring in a simple event tracing library and POC utility

- Import libevtr, a library for abstracting access to an event stream.
libevtr uses its own dump format and can synthesize event attributes
based on known event types.
- Modify ktrdump(8) to be able to dump an event stream to a file
using libevtr.
- Add evtranalyze(1), a proof of concept utility to display events in
a line-oriented text format or to generate an svg file displaying
the events on each processor. This needs quite some work.

show more ...