| /gem5/ |
| H A D | CONTRIBUTING.md | 252 remote: ERROR: [fb1366b] missing Change-Id in commit message footer
|
| H A D | SConstruct | 71 # % cd <path-to-src>/gem5 ; scons /local/foo/build/ALPHA/gem5.debug
72 # % cd /local/foo/build/ALPHA; scons -C <path-to-src>/gem5 gem5.debug
234 # example, for target 'foo/bar/build/ALPHA_SE/arch/alpha/blah.do' we
|
| /gem5/configs/boot/ |
| H A D | nfs-client-dbench.rcS | 53 dd if=/dev/zero of=foo bs=1024k count=512
|
| /gem5/configs/dram/ |
| H A D | lat_mem_rd.py | 258 system.monitor.footprint = MemFootprintProbe()
|
| /gem5/ext/fputils/ |
| H A D | Doxyfile.in | 882 # header.html footer.html stylesheet.css YourConfigFile" and then modify
889 # The HTML_FOOTER tag can be used to specify a personal HTML footer for
891 # standard footer.
938 # If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML
1265 # The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for
1266 # the generated latex document. The footer should contain everything after
1268 # standard footer. Notice: only use this tag if you know what you are doing!
|
| /gem5/ext/ |
| H A D | git-commit-msg | 73 # - assume textLine+ to be a footer until proven otherwise
74 # - exception: the first block is not footer (as it is the title)
78 # aren't footer
79 # - in END, the last textLine+ block is available for footer parsing
83 # is a footer, the first block is not.
85 footerComment = 0
101 # Count blank lines outside footer comments
102 /^$/ && (footerComment == 0) {
107 # Catch footer comment
109 footerComment
[all...] |
| /gem5/ext/googletest/googlemock/docs/ |
| H A D | CheatSheet.md | 9 class Foo {
11 virtual ~Foo();
18 (note that `~Foo()` **must** be virtual) we can define its mock as
22 class MockFoo : public Foo {
68 MOCK_METHOD_1_WITH_CALLTYPE(STDMETHODCALLTYPE, Foo, bool(int n));
88 MockFoo foo; // #2
90 ON_CALL(foo, GetSize()) // #3
94 EXPECT_CALL(foo, Describe(5)) // #4
99 EXPECT_EQ("good", MyProductionFunction(&foo)); // #5
258 1. a native array passed by reference (e.g. in `Foo(cons
[all...] |
| H A D | CookBook.md | 8 readability, it is recommended to write `using ::testing::Foo;` once in
9 your file before using the name `Foo` defined by Google Mock. We omit
25 class Foo {
37 class MockFoo : public Foo {
54 class Foo {
57 // Must be virtual as we'll inherit from Foo.
58 virtual ~Foo();
69 class MockFoo : public Foo {
84 class MockFoo : public Foo {
86 using Foo
[all...] |
| H A D | DesignDoc.md | 77 ACTION(Foo) {
84 defines an action `Foo()` that invokes argument #2 (a function pointer)
177 ACTION(Foo) {
201 | `ACTION(Foo)` | `Foo()` | `FooAction` |
238 * They have subtle semantics that easily confuses new users. For example, in expression `_1++ + foo++`, `foo` will be incremented only once where the expression is evaluated, while `_1` will be incremented every time the unnamed function is invoked. This is far from intuitive.
|
| H A D | ForDummies.md | 111 When you define a mock class, you need to decide where to put its definition. Some people put it in a `*_test.cc`. This is fine when the interface being mocked (say, `Foo`) is owned by the same person or team. Otherwise, when the owner of `Foo` changes it, your test could break. (You can't really expect `Foo`'s maintainer to fix every test that uses `Foo`, can you?)
113 So, the rule of thumb is: if you need to mock `Foo` and it's owned by others, define the mock class in `Foo`'s package (better, in a `testing` sub-package such that you can clearly separate production code and testing utilities), and put it in a `mock_foo.h`. Then everyone can reference `mock_foo.h` from their tests. If `Foo` ever changes, there is only one copy of `MockFoo` to change, and only tests that depend on the changed methods need to be fixed.
115 Another way to do it: you can introduce a thin layer `FooAdaptor` on top of `Foo` and code to this new interface. Since you own `FooAdaptor`, yo
[all...] |
| H A D | FrequentlyAskedQuestions.md | 85 *os << "the Foo property is " << value.GetFoo();
105 *listener << "the Foo property is " << value.GetFoo();
258 class Foo {
263 class MockFoo : public Foo {
270 warning C4301: 'MockFoo::Bar': overriding virtual function only differs from 'Foo::Bar' by const/volatile qualifier
276 warning C4373: 'MockFoo::Bar': virtual function overrides 'Foo::Bar', previous versions of the compiler did not override when parameters only differed by const/volatile qualifiers
280 `const` modifier is _ignored_. Therefore, the `Foo` base class above
283 class Foo {
294 _declaration_, we recommend to remove it in both `Foo` and `MockFoo`.
322 EXPECT_CALL(foo, Ba
[all...] |
| /gem5/ext/googletest/googlemock/docs/v1_5/ |
| H A D | CheatSheet.md | 9 class Foo {
11 virtual ~Foo();
18 (note that `~Foo()` **must** be virtual) we can define its mock as
22 class MockFoo : public Foo {
68 MOCK_METHOD_1_WITH_CALLTYPE(STDMETHODCALLTYPE, Foo, bool(int n));
88 MockFoo foo; // #2
90 ON_CALL(foo, GetSize()) // #3
94 EXPECT_CALL(foo, Describe(5)) // #4
99 EXPECT_EQ("good", MyProductionFunction(&foo)); // #5
235 1. a native array passed by reference (e.g. in `Foo(cons
[all...] |
| H A D | CookBook.md | 8 readability, it is recommended to write `using ::testing::Foo;` once in
9 your file before using the name `Foo` defined by Google Mock. We omit
25 class Foo {
37 class MockFoo : public Foo {
54 class Foo {
57 // Must be virtual as we'll inherit from Foo.
58 virtual ~Foo();
69 class MockFoo : public Foo {
84 class MockFoo : public Foo {
86 using Foo
[all...] |
| H A D | ForDummies.md | 111 When you define a mock class, you need to decide where to put its definition. Some people put it in a `*_test.cc`. This is fine when the interface being mocked (say, `Foo`) is owned by the same person or team. Otherwise, when the owner of `Foo` changes it, your test could break. (You can't really expect `Foo`'s maintainer to fix every test that uses `Foo`, can you?)
113 So, the rule of thumb is: if you need to mock `Foo` and it's owned by others, define the mock class in `Foo`'s package (better, in a `testing` sub-package such that you can clearly separate production code and testing utilities), and put it in a `mock_foo.h`. Then everyone can reference `mock_foo.h` from their tests. If `Foo` ever changes, there is only one copy of `MockFoo` to change, and only tests that depend on the changed methods need to be fixed.
115 Another way to do it: you can introduce a thin layer `FooAdaptor` on top of `Foo` and code to this new interface. Since you own `FooAdaptor`, yo
[all...] |
| H A D | FrequentlyAskedQuestions.md | 81 *os << "the Foo property is " << value.GetFoo();
101 *listener << "the Foo property is " << value.GetFoo();
254 class Foo {
259 class MockFoo : public Foo {
266 warning C4301: 'MockFoo::Bar': overriding virtual function only differs from 'Foo::Bar' by const/volatile qualifier
272 warning C4373: 'MockFoo::Bar': virtual function overrides 'Foo::Bar', previous versions of the compiler did not override when parameters only differed by const/volatile qualifiers
276 `const` modifier is _ignored_. Therefore, the `Foo` base class above
279 class Foo {
290 _declaration_, we recommend to remove it in both `Foo` and `MockFoo`.
318 EXPECT_CALL(foo, Ba
[all...] |
| /gem5/ext/googletest/googlemock/docs/v1_6/ |
| H A D | CheatSheet.md | 9 class Foo {
11 virtual ~Foo();
18 (note that `~Foo()` **must** be virtual) we can define its mock as
22 class MockFoo : public Foo {
68 MOCK_METHOD_1_WITH_CALLTYPE(STDMETHODCALLTYPE, Foo, bool(int n));
88 MockFoo foo; // #2
90 ON_CALL(foo, GetSize()) // #3
94 EXPECT_CALL(foo, Describe(5)) // #4
99 EXPECT_EQ("good", MyProductionFunction(&foo)); // #5
240 1. a native array passed by reference (e.g. in `Foo(cons
[all...] |
| H A D | CookBook.md | 8 readability, it is recommended to write `using ::testing::Foo;` once in
9 your file before using the name `Foo` defined by Google Mock. We omit
25 class Foo {
37 class MockFoo : public Foo {
54 class Foo {
57 // Must be virtual as we'll inherit from Foo.
58 virtual ~Foo();
69 class MockFoo : public Foo {
84 class MockFoo : public Foo {
86 using Foo
[all...] |
| H A D | ForDummies.md | 111 When you define a mock class, you need to decide where to put its definition. Some people put it in a `*_test.cc`. This is fine when the interface being mocked (say, `Foo`) is owned by the same person or team. Otherwise, when the owner of `Foo` changes it, your test could break. (You can't really expect `Foo`'s maintainer to fix every test that uses `Foo`, can you?)
113 So, the rule of thumb is: if you need to mock `Foo` and it's owned by others, define the mock class in `Foo`'s package (better, in a `testing` sub-package such that you can clearly separate production code and testing utilities), and put it in a `mock_foo.h`. Then everyone can reference `mock_foo.h` from their tests. If `Foo` ever changes, there is only one copy of `MockFoo` to change, and only tests that depend on the changed methods need to be fixed.
115 Another way to do it: you can introduce a thin layer `FooAdaptor` on top of `Foo` and code to this new interface. Since you own `FooAdaptor`, yo
[all...] |
| H A D | FrequentlyAskedQuestions.md | 85 *os << "the Foo property is " << value.GetFoo();
105 *listener << "the Foo property is " << value.GetFoo();
258 class Foo {
263 class MockFoo : public Foo {
270 warning C4301: 'MockFoo::Bar': overriding virtual function only differs from 'Foo::Bar' by const/volatile qualifier
276 warning C4373: 'MockFoo::Bar': virtual function overrides 'Foo::Bar', previous versions of the compiler did not override when parameters only differed by const/volatile qualifiers
280 `const` modifier is _ignored_. Therefore, the `Foo` base class above
283 class Foo {
294 _declaration_, we recommend to remove it in both `Foo` and `MockFoo`.
322 EXPECT_CALL(foo, Ba
[all...] |
| /gem5/ext/googletest/googlemock/docs/v1_7/ |
| H A D | CheatSheet.md | 9 class Foo {
11 virtual ~Foo();
18 (note that `~Foo()` **must** be virtual) we can define its mock as
22 class MockFoo : public Foo {
68 MOCK_METHOD_1_WITH_CALLTYPE(STDMETHODCALLTYPE, Foo, bool(int n));
88 MockFoo foo; // #2
90 ON_CALL(foo, GetSize()) // #3
94 EXPECT_CALL(foo, Describe(5)) // #4
99 EXPECT_EQ("good", MyProductionFunction(&foo)); // #5
253 1. a native array passed by reference (e.g. in `Foo(cons
[all...] |
| H A D | CookBook.md | 8 readability, it is recommended to write `using ::testing::Foo;` once in
9 your file before using the name `Foo` defined by Google Mock. We omit
25 class Foo {
37 class MockFoo : public Foo {
54 class Foo {
57 // Must be virtual as we'll inherit from Foo.
58 virtual ~Foo();
69 class MockFoo : public Foo {
84 class MockFoo : public Foo {
86 using Foo
[all...] |
| H A D | ForDummies.md | 111 When you define a mock class, you need to decide where to put its definition. Some people put it in a `*_test.cc`. This is fine when the interface being mocked (say, `Foo`) is owned by the same person or team. Otherwise, when the owner of `Foo` changes it, your test could break. (You can't really expect `Foo`'s maintainer to fix every test that uses `Foo`, can you?)
113 So, the rule of thumb is: if you need to mock `Foo` and it's owned by others, define the mock class in `Foo`'s package (better, in a `testing` sub-package such that you can clearly separate production code and testing utilities), and put it in a `mock_foo.h`. Then everyone can reference `mock_foo.h` from their tests. If `Foo` ever changes, there is only one copy of `MockFoo` to change, and only tests that depend on the changed methods need to be fixed.
115 Another way to do it: you can introduce a thin layer `FooAdaptor` on top of `Foo` and code to this new interface. Since you own `FooAdaptor`, yo
[all...] |
| H A D | FrequentlyAskedQuestions.md | 85 *os << "the Foo property is " << value.GetFoo();
105 *listener << "the Foo property is " << value.GetFoo();
258 class Foo {
263 class MockFoo : public Foo {
270 warning C4301: 'MockFoo::Bar': overriding virtual function only differs from 'Foo::Bar' by const/volatile qualifier
276 warning C4373: 'MockFoo::Bar': virtual function overrides 'Foo::Bar', previous versions of the compiler did not override when parameters only differed by const/volatile qualifiers
280 `const` modifier is _ignored_. Therefore, the `Foo` base class above
283 class Foo {
294 _declaration_, we recommend to remove it in both `Foo` and `MockFoo`.
322 EXPECT_CALL(foo, Ba
[all...] |
| /gem5/ext/googletest/googlemock/include/gmock/ |
| H A D | gmock-actions.h | 55 // To implement an action Foo, define:
56 // 1. a class FooAction that implements the ActionInterface interface, and
58 // const FooAction*.
197 // // Sets the default value for type T to be foo.
198 // DefaultValue<T>::Set(foo);
412 // class FooAction {
423 // MakePolymorphicAction(object) where object has type FooAction. See
471 // MakePolymorphicAction(foo);
473 // PolymorphicAction<TypeOfFoo>(foo);
520 // Foo fo
[all...] |
| H A D | gmock-cardinalities.h | 48 // To implement a cardinality Foo, define:
49 // 1. a class FooCardinality that implements the
52 // const FooCardinality*.
|