Hi,

I'm going to release a new version of pat. But I found some problems. The 
significant problem for me is to run all examples to ensure the correctness of 
pat.

For now, we don't have testing script to run all examples automatically. Is 
there anyone willing to contribute?

Luba.

When I compile pat with 2.6.2, I got many of the warning:
{{{
ld: warning: direct access in 
pat::testing::GetBoolAssertionFailureMessage(pat::testing::AssertionResult 
const&, char const*, char const*, char const*) to global weak symbol VTT for 
pat::BasicOStrStream<char, std::__1::char_traits<char>, 
std::__1::allocator<char> > means the weak symbol cannot be overridden at 
runtime. This was likely caused by different translation units being compiled 
with different visibility settings.
}}}

I'm not sure the causes of the warning. I'm trying to change default visibility 
to remove this warning.

In order to let "pat"'s source code become more readable, it's necessary to 
separate "pat.cpp" into several files, such as:
- lib/Support/Timer.cpp
- lib/Support/ManagedStatic.h
- lib/Support/ManagedStatic.cpp
- lib/ADT/Color.h
- lib/ADT/Color.cpp
- lib/Support/OStream.h
- lib/Support/OStream.cpp
- lib/Core/pat.cpp
- lib/Listeners/PrettyPrinter.cpp

Dears,

pat requests <sys/times.h> and <sys/time.h>. However, I don't see any checking 
of these headers. I will add the checking in setup_pat.m4

Luba

What steps will reproduce the problem?
I download pat via git at pat/ directory.

1. cp ./pat/utils/build-script/build.sh .
2. ./build.sh ./pat dbg

What do you see?
I got the compilation errors:
{{{
home/luba/Skymizer/pat/./pat.git/lib/ADT/Color.cpp: In member function 'void 
pat::Color::setColor(std::ostream&)':
/home/luba/Skymizer/pat/./pat.git/lib/ADT/Color.cpp:32:7: error: no match for 
'operator<<' (operand types are 'std::ostream {aka std::basic_ostream<char>}' 
and 'const char [3]')
   pOS << "\033[";
       ^
/home/luba/Skymizer/pat/./pat.git/lib/ADT/Color.cpp:32:7: note: candidates are:
In file included from /home/luba/Skymizer/pat/./pat.git/lib/ADT/Color.cpp:9:0:
/home/luba/Skymizer/pat/./pat.git/include/pat/ADT/Color.h:61:10: note: 
std::ostream& std::operator<<(std::ostream&, pat::Color::kColor)
 ostream& operator<<(ostream& pOS, pat::Color::kColor pColor);
          ^
/home/luba/Skymizer/pat/./pat.git/include/pat/ADT/Color.h:61:10: note:   no 
known conversion for argument 2 from 'const char [3]' to 'pat::Color::kColor'
/home/luba/Skymizer/pat/./pat.git/include/pat/ADT/Color.h:60:10: note: 
std::ostream& std::operator<<(std::ostream&, pat::Color)
 ostream& operator<<(ostream& pOS, pat::Color pColor);
          ^
/home/luba/Skymizer/pat/./pat.git/include/pat/ADT/Color.h:60:10: note:   no 
known conversion for argument 2 from 'const char [3]' to 'pat::Color'

# ignore the rest.
}}}

I've tried to use "perf sched" to measure the execution time of test-cases on 
linux-x86 and linux-arm.
But I cannot execute "perf sched" on both platforms.

This issue is created to record the development process of perf_event. At the 
time this issue was created, the finest grained timer in pat is gettimeofday 
and didn't provide any profiling details.

Dears,

When I'm in the development of the bold project, I find I really want pat to 
provide ASSERT_EQ/NE macros.

Is there anyone responsible for this?

Luba

Different Unix has different PMU interfaces.
For examples, Linux uses perf_events and FreeBSD uses HWPMC. Both of them 
control the hardware performance unit though very different interfaces.

We should distinguish these operating system at configure script and repolish 
Support/ directory structure.

Write "HowToUse" page for guiding users to write their test-case to use "pat" 
to analysis their program's performance.

PAT_F(IntegerTest, eq_test)
{
  int a = 10;
  EXPECT_EQ(++a, 12);
}

[----------] 1 test from IntegerTest.
[ RUN      ] IntegerTest.eq_test
[  FAILED  ] 
IntegerTest.cpp:5: error: failed to expect
Value of: (++a == 12)
  Actual:   12
  Expected: 12

  Actual:   11
  Expected: 12