Пожалуйста, включите JavaScript.
Главная
Обзор
Помощь
Вход
visus
/
dds
Следить
1
В избранное
0
Форкнуть
0
Код
Задачи
0
Pull Request'ы
0
Релизы
0
Вики
Активность
Вы не можете выбрать более 25 тем
Темы должны начинаться с буквы или цифры, могут содержать дефисы(-) и должны содержать не более 35 символов.
488
коммитов
6
Ветки
Дерево:
87f60a1e39
better_mac_paths
compile_link_flags
default_compile_flags
gnu_extensions
mac_paths
main
Ветки
Теги
${ item.name }
Создать ветку
${ searchTerm }
из '87f60a1e39'
${ noResults }
dds
/
tests
/
db
/
project
/
src
/
foo.hpp
foo.hpp
43B
Исходник
Normal View
История
Attach mtimes to individual deps, not files. Fixes a miscompile (!!) Fix bug: - Assume X and Y depend on Z - X and Y both compile clean. - A change is made to Z - X and Y are now "out-of-date," and marked to compile. - The change causes a failure in X, but Y still compiles clean. - Because X compiles clean, the database will be updated and store the new mtime of Z! - Attempting to compile again, the mtime of Z will not be considered "changed" since the last compile. - X depends on Z, but Z is not marked "changed," and X will not be recompiled, even though it is still in a dirty state! - Linking of X and Y produces wild results. UB. ORD NDR. Badness. The fix is to have the edges in the graph between inputs and outputs store the mtime of the input, rather than to store that mtime on the file itself. Thus, each individual relationship between inputs and outputs will track the "outdated-ness" of themselves. This also adds a test which can correctly reproduce the issue in absense of the fix.
5 лет назад
1
2
3
4
#pragma once
int value_1();
int value_2();